linux-kernel - Re: [PATCH 1/2] x86: mce: kdump: use under_crashdumping to turn off MCE in all CPUs together

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150223170653.GA16699@pd.tnic>
Date:	Mon, 23 Feb 2015 18:06:53 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Naoya Horiguchi <nao.horiguchi@...il.com>
Cc:	Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
	Tony Luck <tony.luck@...el.com>,
	Vivek Goyal <vgoyal@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Junichi Nomura <j-nomura@...jp.nec.com>,
	Kiyoshi Ueda <k-ueda@...jp.nec.com>
Subject: Re: [PATCH 1/2] x86: mce: kdump: use under_crashdumping to turn off
 MCE in all CPUs together

On Tue, Feb 24, 2015 at 12:41:11AM +0900, Naoya Horiguchi wrote:
> What I saw was that once in hundreds of kdump and reboot cycle we hit
> kdump failure and panic with "Timeout synchronizing machine check over
> CPUs" message.

Ok, but this doesn't necessarily mean you're seeing an MCE.

Or perhaps your NMI shooting down is causing an MCE once in a hundred
kdump cycles, i.e. I'm looking at nmi_shootdown_cpus().

Can you send me a dmesg from such a case where this happens? The more
verbose, the better.

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/