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. Thanks very much for reading and helping :-) Regards, TL -- -
| Mariusz Kozlowski | [PATCH 01] kmalloc + memset conversion co kzalloc |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Jeremy Allison | Re: [RFC] Heads up on sys_fallocate() |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| David Miller | Re: [GIT]: Networking |
| Jeff Garzik | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
