Some architectures already have their own recursive
locking for oopses and we have another version for
serialising dump_stack.
Create a common version and use it everywhere (oopses,
BUGs, WARNs, dump_stack, soft lockups and hard lockups).
Dunno. I've had cases where the simultaneity of the
On Tue, Feb 24, 2015 at 01:39:46AM -0800, Arjan van de Ven wrote:
one of the question is if you want to serialize, or if you just want
to label. If you take a cookie (could just be a monotonic increasing
number) at the start of the oops and then prefix/postfix the stack
printing with that
Every now and then I end up with an undebuggable issue because multiple
CPUs hit something at the same time and everything is interleaved:
CR: 4882 XER:
,RI
c003dc72fd10
,LE
d65b84e8
Instruction dump:
MSR:
* Anton Blanchard an...@samba.org wrote:
Every now and then I end up with an undebuggable issue
because multiple CPUs hit something at the same time and
everything is interleaved:
CR: 4882 XER:
,RI
c003dc72fd10
,LE
