Strange reboots on 2.6.29-rc6-wl
Hello!
I've two Lenovo X200 here, same config and same kernel version (2.6.29-rc7-wl-ikn, from wireless-testing, v2.6.29-rc7-17155-g2f7ab92).
One reboots after half a second after displaying a message Probing for edd (or similar). I tried with and without edd=off, no changes.
The same happens with v2.6.29-rc7-32930-g5434dd7 (iwlwifi-2.6).
Anyone an idea, what maybe the reason for that behaviour?
Nico
Signature · 4 lines
Think about Free and Open Source Software (FOSS). http://nico.schottelius.org/documentations/foss/the-term-foss/ PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
Quoted 11 lines · Nico Schottelius
Hello!
I've two Lenovo X200 here, same config and same kernel version (2.6.29-rc7-wl-ikn, from wireless-testing, v2.6.29-rc7-17155-g2f7ab92).
One reboots after half a second after displaying a message Probing for edd (or similar). I tried with and without edd=off, no changes.
The same happens with v2.6.29-rc7-32930-g5434dd7 (iwlwifi-2.6).
Anyone an idea, what maybe the reason for that behaviour?
No clue. But since you clearly are comfortable with git and building your own kernels, perhaps you can use git bisect to suggest which commit is broken? :-)
John
Signature · 2 lines
John W. Linville Someday the world will need a hero, and you [email protected] might be all we have. Be ready.
John W. Linville [Fri, Mar 13, 2009 at 04:41:01PM -0400]:
Quoted 9 lines · Nico Schottelius
Quoted 8 lines
Hello!
I've two Lenovo X200 here, same config and same kernel version (2.6.29-rc7-wl-ikn, from wireless-testing, v2.6.29-rc7-17155-g2f7ab92).
One reboots after half a second after displaying a message Probing for edd (or similar). I tried with and without edd=off, no changes.
Quoted 7 lines
Quoted 3 lines
The same happens with v2.6.29-rc7-32930-g5434dd7 (iwlwifi-2.6).
Anyone an idea, what maybe the reason for that behaviour?
No clue. But since you clearly are comfortable with git and building your own kernels, perhaps you can use git bisect to suggest which commit is broken? :-)
It seems there's something different broken, all newly built kernels are instantly rebooting. All are displaying the "edd=off" warning message.
The gcc version is slightly different (4.1.3 vs. 4.3.3, both Debian), but I'm already running next-20090306 compiled with this compiler.
Has anyone a clue on howto debug the build environment or debugging the kernel before it's getting booted?
Nico
Signature · 4 lines
Think about Free and Open Source Software (FOSS). http://nico.schottelius.org/documentations/foss/the-term-foss/ PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
Quoted 3 lines · Nico -telmich- Schottelius
Has anyone a clue on howto debug the build environment or debugging the kernel before it's getting booted?
If you have a serial console you can probably get output on that. If you have flipped EMBEDDED to Y then you might also have to enable EARLY_PRINTK. Another trick might be to turn set BOOT_PRINTK_DELAY (Kernel hacking -> Delay each boot printk message by N milliseconds) to something like 2000 and see if you can read/catch the messages before the kernel reboots...
Failing that start a git bisection (
http://www.kernel.org/doc/local/git-quick.html#bisect or
http://www.stardust.webpages.pl/files/handbook/handbook-en-0.3-rc1.pdf ) from the last good kernel...
Signature · 1 line
Sitsofe | http://sucs.org/~sits/
Sitsofe Wheeler [Tue, Mar 17, 2009 at 02:57:53PM +0000]:
Quoted 6 lines · Nico -telmich- Schottelius
Quoted 3 lines
Has anyone a clue on howto debug the build environment or debugging the kernel before it's getting booted?
If you have a serial console you can probably get output on that.
There's no native serial port on the machine :-/
Quoted 5 lines
If you have flipped EMBEDDED to Y then you might also have to enable
EARLY_PRINTK. Another trick might be to turn setBOOT_PRINTK_DELAY(Kernel hacking -> Delay each boot printk message by N milliseconds) to something like 2000 and see if you can read/catch the messages before the kernel reboots...
I've EARLY_PRINTK set, but other than the edd probing message I don't see anything.
Quoted 4 lines
Failing that start a git bisection (
http://www.kernel.org/doc/local/git-quick.html#bisect or
http://www.stardust.webpages.pl/files/handbook/handbook-en-0.3-rc1.pdf ) from the last good kernel...
I really don't think that it's the kernel's fault, because _all_ new versions I compile instantly reboot.
Last one I tried was v2.6.29-rc8-241-g65c2449 (linux-2.6). Isn't there some flag to enable step by step execution (like in gdb)?
Or is somebody else using Debian squeeze with latest updates?
Sincerly,
Nico
Signature · 4 lines
Think about Free and Open Source Software (FOSS). http://nico.schottelius.org/documentations/foss/the-term-foss/ PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
Quoted 10 lines · Nico -telmich- Schottelius
Sitsofe Wheeler [Tue, Mar 17, 2009 at 02:57:53PM +0000]:
Quoted 6 lines · Nico -telmich- Schottelius
Quoted 3 lines
Has anyone a clue on howto debug the build environment or debugging the kernel before it's getting booted?
If you have a serial console you can probably get output on that.
There's no native serial port on the machine :-/
Quoted 8 lines
Quoted 5 lines
If you have flipped EMBEDDED to Y then you might also have to enable
EARLY_PRINTK. Another trick might be to turn setBOOT_PRINTK_DELAY(Kernel hacking -> Delay each boot printk message by N milliseconds) to something like 2000 and see if you can read/catch the messages before the kernel reboots...I've
EARLY_PRINTKset, but other than the edd probing message I don't see anything.
What about when you set BOOT_PRINTK_DELAY to a value high enough to cause pauses - do you see more messages? Additionally are booting your kernel without the quiet option? Have you checked to make sure the kernel isn't set to reboot on oops/panic etc? Are you using any binary drivers?
Quoted 7 lines
Quoted 4 lines
Failing that start a git bisection (
http://www.kernel.org/doc/local/git-quick.html#bisect or
http://www.stardust.webpages.pl/files/handbook/handbook-en-0.3-rc1.pdf ) from the last good kernel...I really don't think that it's the kernel's fault, because _all_ new versions I compile instantly reboot.
So even a freshly compiled 2.6.27 and 2.6.28 reboot instantly?! If even old kernels that worked suddently don't work that hints strongly at hardware errors or a duff compiler toolchain...
You can also make the kernel spit out decompression error messages by enabling CONFIG_X86_VERBOSE_BOOTUP . I guess it would also be wise to make sure CONFIG_DOUBLEFAULT is also set. Are you sure nothing else has changed though? Have you enabled some kernel option that was not set before? Have you changed any BIOS settings recently?
Quoted 2 lines
Last one I tried was v2.6.29-rc8-241-g65c2449 (linux-2.6). Isn't there some flag to enable step by step execution (like in gdb)?
I don't think I undrstand what you mean - the kernel isn't a debugger... If you are running a User Mode Linux kernel or running inside QEMU etc. then you can do what you describe because your "machine" is a program but I think the only way to do that with real hardware is to learn how to use KGDB ( http://kgdb.sourceforge.net ) and have another machine to hand. I suppose you could also sprinkle beep patches/debug printks about the place to see just how far it gets before it reboots...
Signature · 1 line
Sitsofe | http://sucs.org/~sits/
Nico Schottelius [Fri, Mar 13, 2009 at 09:06:57PM +0100]:
Quoted 8 lines
I've two Lenovo X200 here, same config and same kernel version (2.6.29-rc7-wl-ikn, from wireless-testing, v2.6.29-rc7-17155-g2f7ab92).
One reboots after half a second after displaying a message Probing for edd (or similar). I tried with and without edd=off, no changes.
The same happens with v2.6.29-rc7-32930-g5434dd7 (iwlwifi-2.6).
It works again with 2.6.29 (linux-2.6) and next-20090324 (which is otherwise broken)!
Will test iwlwifi & wireless-testing in the next days.
So it was definitely a kernel issue and not userspace.
Nico
Signature · 4 lines
Think about Free and Open Source Software (FOSS). http://nico.schottelius.org/documentations/foss/the-term-foss/ PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C