* Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> Got this (slightly better) oops. Figured out how to use my camera :-)
>
> http://devzero.co.uk/~alistair/oops6.jpeg
this was a bit more useful - shows a softirq wakeup. Could you send me
your vmlinux (bzip -9 compressed, via private mail), your gcc generates
a slightly different code layout so i couldnt match up everything that
might be useful.
> Onto your stack-footprint metric. I don't know what the number means,
> but at a guess it's the size of the stack. Unfortunately, if this is
> the case, it's unlikely to be an overflow causing the crash. Here's a
> grep of dmesg just before the crash.
it could still be near an overflow. To make sure i've changed the oops
printout to also include the current stack left, and the worst-case
stack-left value, and have uploaded the -51-18 kernel - could you try
it? That way we can tell for sure. (note that the maximum-tracker can
not always do an immediate printout of a worst-case - we have to skip
printouts if irqs are disabled. [or we could recurse from within the
scheduler or the printk code] Even in those cases we save the worst-case
stack and print it out as soon as interrupts are enabled again. (The
worst-case stack-left value printed out at oops time is immediate.)
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/
