Bug 11569
Summary: | Panic stop CPUs regression | ||
---|---|---|---|
Product: | Other | Reporter: | Rafael J. Wysocki (rjw) |
Component: | Other | Assignee: | Andi Kleen (andi-bz) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | alan, andi-bz, florian |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.27-rc | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 11167 |
Description
Rafael J. Wysocki
2008-09-14 21:59:44 UTC
Updating description. 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 Any change? 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 commit 4ef702c10b5df18ab04921fc252c26421d4d6c75 Author: Andi Kleen <andi@firstfloor.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. [snip] Please reopen, if this commit of yours does not fix your issue. |