Subject : Don't complain about disabled irqs when the system has paniced
Submitter : Andi Kleen <email@example.com>
Date : 2008-09-02 13:49
References : http://marc.info/?l=linux-kernel&m=122036356127282&w=4
This entry is being used for tracking a regression from 2.6.26. Please don't
close it until the problem is fixed in the mainline.
The problem is actually worse than described in the original report.
panic() calls smp_call_function() which nows allocates memory and complains
about disabled interrupts. Allocating memory or not allowing panic
from interrupt off regionss definitely not a good idea.
I ran into this because it broke machine checks panics.
Andi, has this problem been fixed in mainline?
No it's still broken
Sorry it's definitely still broken. There have been also reports about this
about users hitting the problem.
I haven't gotten around to fix it yet, but it's on my todo list.
Ping on status Andi ?
I guess this is fixed by
Author: Andi Kleen <firstname.lastname@example.org>
Date: Wed May 27 21:56:52 2009 +0200
x86: fix panic with interrupts off (needed for MCE)
For some time each panic() called with interrupts disabled
triggered the !irqs_disabled() WARN_ON in smp_call_function(),
producing ugly backtraces and confusing users.
Please reopen, if this commit of yours does not fix your issue.