* Ingo Molnar <[email protected]> wrote:
> c011ed50 t wakeup_softirqd
> c011ed80 t trigger_softirqs
>
> but it looks pretty weird. DEBUG_STACK_POISON (and the full-debug
> .config i sent) could perhaps uncover other types of stack
> corruptions.
there's one more pretty efficient debugging method:
echo 1 > /proc/sys/kernel/trace_print_at_crash
echo 1 > /proc/sys/kernel/trace_freerunning
and then upon oopses the kernel will print a full execution trace that
led up to the crash. But this definitely needs a serial console to be
usable, as the kernel will print out thousands of trace entries.
(also, since it seems your kernel crashes when trying to print out the
stacktrace, you'd also have to move the print_traces(task) line within
arch/i386/kernel/traps.c:show_trace() to the beginning of that
function.)
Ingo
-
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/
- References:
- Realtime Preemption, 2.6.12, Beginners Guide?
- Re: Realtime Preemption, 2.6.12, Beginners Guide?
- Re: Realtime Preemption, 2.6.12, Beginners Guide?
- Re: Realtime Preemption, 2.6.12, Beginners Guide?
- Re: Realtime Preemption, 2.6.12, Beginners Guide?
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|