2.6.14-rc3-rt10 crashes on boot
Quoted 6 lines · On Sunday October 9 2005 John Rigg wrote:
Steve, thanks for these patches. I got it to compile with 2.6.14-rc3-rt12 but had to change the assembly lines in (patched)
latency.cto__asm__ __volatile__("and %%rsp,%0" : "=r" (stack_left) : "0" (THREAD_SIZE - 1));
Quoted 8 lines
ie.
and' instead ofandl' and%%rsp' instead of%%esp'. Somebody who understandsx86_64assembly better than I do should probably check this before anyone tries using it.
While I was at it I changed a printk arg in line 335 of (patched)latency.c- I think the last %d should be %ld, ie.printk("| new stack-footprint maximum: %s/%d, %ld bytes (out of %ld bytes).\n",
worst_stack_comm, worst_stack_pid, MAX_STACK-worst_stack_left, MAX_STACK);
Ingo, thanks to help from Steve Rostedt I got 2.6.14-rc3-rt12 to compile with CONFIG_DEBUG_STACKOVERFLOW=y on x86_64 smp. Unfortunately if I enable it along with latency tracing (which is causing the crash during boot) it crashes so early that I can't get anything from the serial console, even using earlyprintk. All I get is a blank screen for a few seconds then the machine reboots.
I have all other debugging options disabled (apart from necessary dependencies for these two). This of course means that I can't confirm whether the crash is caused by stack overflow.
With latency tracing disabled but CONFIG_DEBUG_STACKOVERFLOW=y the kernel boots and runs fine.
BTW this is still with initrd. If the stack footprint is likely to be smaller with initramfs I'll give it a try, but it'll be a few days before I can set this up (I still have to work out how to use initramfs).
John