On Wed, 2010-01-13 at 10:13 -0700, Bjorn Helgaas wrote: > On Wednesday 13 January 2010 12:15:00 am Émeric Maschino wrote: > > 2010/1/11 Bjorn Helgaas <bjorn.helgaas@xxxxxx>: > > > Right? I'm a bit confused because that should have been what you were > > > testing here: http://marc.info/?l=linux-ia64&m=126290536216298&w=2, > > > unless you applied the patch by hand and made a mistake. > > > > I've probably incorrectly applied your patches without restarting from > > the original file at each attempt. Anyway, it's fine now, thanks. > > > > > I'm afraid I won't be much help with the DRM issue below. I think > > > you'll have better luck with the dri-devel people now. If this is > > > a regression and you can identify an old working kernel, that might > > > help. > > > > I've performed regression tests. The problem appears with kernel > > 2.6.30. Last working kernel is 2.6.29.6. I'm not a kernel developer, > > but could this be due to this commit > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=955b12def42e83287c1bdb1411d99451753c1391? > > Nice work identifying working and non-working versions! > > I don't know how much time and energy you want to devote to this, but > I think there are two ways we can make progress: > > 1) Try to convince DRM folks to help debug this. If I had to guess I'd go with b674137755bbe2750f997a2a1264db3cdf8abcb3 But maybe a bisect would be more definite. Dave. > > 2) Use git bisect[1] between v2.6.29 and v2.6.30. This looks like > about 13 kernel rebuild/test cycles. I don't see the stable > releases like 2.6.29.6 in the git repo, but you won't lose much > by starting with 2.6.29. > > [1] http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html > > Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|