On 9/16/07, Satyam Sharma <[EMAIL PROTECTED]> wrote: > Hi Timo, > > > On 7/15/07, Timo Lindemann <[EMAIL PROTECTED]> wrote: > > To sum this up: > > > > the userspace 2.6.20.6 (the "good" kernel) and 2.6.22 (the "bad" kernel) > > were compiled in is exactly the same setup. I recompiled "good" to check > > for that, earlier, but "good" also works then. > > > > "good" does not exhibit the printks I placed in the section (the same > > ones I did for "bad"), making it plausible that the section is not > > executed at all. > > > > dmesg is not captured to disk, netconsole and serial console also do not > > work (they both did in the "good" kernel). Also, my keyboard does not > > work with "bad" during that phase -- Magic SysRq is also not working then. > > > > I can try to hook up the laptop to an external monitor to capture some > > more dmesg, and just shoot a photo, but I am right now trying to work > > with git, as Satyam suggested. > > Any updates on this for us? Or did the kernel start booting magically again > ca. 2.6.23-rc6? ;-)
Should again add that best would still be to simply git-bisect Linus' (mainline) kernel tree between 2.6.20 (not 2.6.20.6) and 2.6.22 and just find the commit after which your box stops booting ... > Anyway, it appears the bug got introduced sometime between 2.6.20 and > 2.6.22 so probably bugzilla becomes a better place to track this one. Could > you open up a bug report (similar to your original post) there? > > Thanks, > > Satyam > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/