* Alistair John Strachan <[email protected]> wrote:
> > 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?
usually such loops happen if the stack has been overflown and critical
information that lies on the bottom of the stack (struct thread_info) is
overwritten. Then we often cannot even perform simple printks. Stack
overflow debugging wont prevent the crash, but might give a better
traceback.
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]
| |
 |