Re: frequent lockups in 3.18rc4

From: Dave Jones
Date: Tue Nov 18 2014 - 17:03:15 EST

On Tue, Nov 18, 2014 at 04:55:40PM -0500, Don Zickus wrote:

> > So here we mangle CPU3 in and lose the backtrace for cpu0, which might
> > be the real interesting one ....
> Can you provide another dump? The hope is we get something not mangled?

Working on it..

> The other option we have done in RHEL is panic the system and let kdump
> capture the memory. Then we can analyze the vmcore for the stack trace
> cpu0 stored in memory to get a rough idea where it might be if the cpu
> isn't responding very well.

I don't know if it's because of the debug options I typically run with,
or that I'm perpetually cursed, but I've never managed to get kdump to
do anything useful. (The last time I tried it was actively harmful in
that not only did it fail to dump anything, it wedged the machine so
it didn't reboot after panic).

Unless there's some magic step missing from the documentation at
then I'm not optimistic it'll be useful.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at