![]() | |||||||||||||
Messages in this thread |
Linus Torvalds wrote: >On Tue, 16 Aug 2005, Helge Hafting wrote: > > >>This was interesting. At first, lots of kernels just kept working, >>I almost suspected I was doing something wrong. Then the second last kernel >>recompiled a lot of DRM stuff - and the crash came back! >>The kernel after that worked again, and so the final message was: >> >>561fb765b97f287211a2c73a844c5edb12f44f1d is first bad commit >> >> > >Ok, that definitely looks bogus. > >That commit should not matter at _all_, it only changes ppc64 specific >things. > >If the bug is sometimes hard to trigger, maybe one of the "good" kernels >wasn't good after all. That would definitely throw a wrench in the >bisection. > > The bisection search: a46e812620bd7db457ce002544a1a6572c313d8a good e0b98c79e605f64f263ede53344f283f5e0548be good fd3113e84e188781aa2935fbc4351d64ccdd171b good 2757a71c3122c7653e3dd8077ad6ca71efb1d450 good ba17101b41977f124948e0a7797fdcbb59e19f3e good, this one has got more testing, as my default kernel to boot for the moment. saw lots of drm recompile for the next one: 561fb765b97f287211a2c73a844c5edb12f44f1d bad 6ade43fbbcc3c12f0ddba112351d14d6c82ae476 good I'll test this one more to see if it is a false positive, and I'll also test a known bad kernel without DRM. Helge Hafting - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-08-16 10:40 [from the cache] ©2003-2008 | |||||||||||||