Messages in this thread | | | Date | Mon, 23 Feb 2015 14:58:42 +0100 | From | Borislav Petkov <> | Subject | Re: [PATCH 1/2] x86: mce: kdump: use under_crashdumping to turn off MCE in all CPUs together |
| |
On Mon, Feb 23, 2015 at 10:01:50PM +0900, Naoya Horiguchi wrote: > userspace. What end users see is like these timeout messages: > - "Timeout: Not all CPUs entered broadcast exception handler", > - "Timeout: Subject CPUs unable to finish machine check processing", > - "Timeout: Monarch CPU unable to finish machine check processing", or > - "Timeout: Monarch CPU did not finish machine check processing". > These are informative for developers like us, but confusing for end users.
Those messages won't go out if tolerant level is > 1 AFAICT and from looking at mce_timed_out() and the machine wouldn't panic, for that matter.
So what is the actual problem you're seeing?
Cores timeoutting when a machine check happens during entering kdump or you not wanting cores to panic due to a machine check while the machine enters kdump?
Something else?
-- Regards/Gruss, Boris.
ECO tip #101: Trim your mails when you reply. --
| |