* 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.
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/
[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]
| |
 |