On Thursday 07 Jul 2005 12:29, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > Unfortunately, since this is called when the kernel crashes, it's
> > impossible for me to capture any messages prior to this spam, if there
> > even are any.
>
> this is where serial logging (or netconsole/netlogging) may be useful.
>
> do you have DEBUG_STACKOVERFLOW and latency tracing still enabled? The
> combination of those two options is pretty good at detecting stack
> overflows. Also, you might want to enable CONFIG_4KSTACKS, that too
> disturbs the stack layout enough so that the error message may make it
> to the console.
I already have 4KSTACKS on. Latency tracing is enabled, but STACKOVERFLOW
isn't; I'll just reenable everything again until we fix this. Do you think if
I removed the printk() line I might get some useful information, before it
does the stack trace?
I'm happy enough to work with this indefinitely now, at least I have a certain
cause for the lockups, so I can continue to use the machine for R&D.
--
Cheers,
Alistair.
personal: alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student: CS/CSim Undergraduate
contact: 1F2 55 South Clerk Street,
Edinburgh. EH8 9PP.
-
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/
