From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751382AbdAWOvF (ORCPT ); Mon, 23 Jan 2017 09:51:05 -0500 Received: from mail.skyhub.de ([78.46.96.112]:47534 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751098AbdAWOvE (ORCPT ); Mon, 23 Jan 2017 09:51:04 -0500 Date: Mon, 23 Jan 2017 15:50:56 +0100 From: Borislav Petkov To: xlpang@redhat.com Cc: x86@kernel.org, linux-kernel@vger.kernel.org, kexec@lists.infradead.org, Tony Luck , Ingo Molnar , Dave Young , Prarit Bhargava , Junichi Nomura , Kiyoshi Ueda , Naoya Horiguchi Subject: Re: [PATCH] x86/mce: Keep quiet in case of broadcasted mce after system panic Message-ID: <20170123145056.fyraeehjfnwmmfb6@pd.tnic> References: <1485158511-22374-1-git-send-email-xlpang@redhat.com> <20170123125157.u2kefedwpvgcdyfo@pd.tnic> <588606B9.3070604@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <588606B9.3070604@redhat.com> User-Agent: NeoMutt/20161014 (1.7.1) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 23, 2017 at 09:35:53PM +0800, Xunlei Pang wrote: > One possible timing sequence would be: > 1st kernel running on multiple cpus panicked > then the crash dump code starts > the crash dump code stops the others cpus except the crashing one > 2nd kernel boots up on the crash cpu with "nr_cpus=1" > some broadcasted mce comes on some cpu amongst the other cpus(not the crashing cpu) Where does this broadcasted MCE come from? The crash dump code triggered it? Or it happened before the panic()? Are you talking about an *actual* sequence which you're experiencing on real hw or is this something hypothetical? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.skyhub.de ([78.46.96.112]) by bombadil.infradead.org with esmtp (Exim 4.87 #1 (Red Hat Linux)) id 1cVfyG-0006De-0H for kexec@lists.infradead.org; Mon, 23 Jan 2017 14:51:49 +0000 Date: Mon, 23 Jan 2017 15:50:56 +0100 From: Borislav Petkov Subject: Re: [PATCH] x86/mce: Keep quiet in case of broadcasted mce after system panic Message-ID: <20170123145056.fyraeehjfnwmmfb6@pd.tnic> References: <1485158511-22374-1-git-send-email-xlpang@redhat.com> <20170123125157.u2kefedwpvgcdyfo@pd.tnic> <588606B9.3070604@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <588606B9.3070604@redhat.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: xlpang@redhat.com Cc: Prarit Bhargava , Kiyoshi Ueda , Tony Luck , x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Ingo Molnar , Junichi Nomura , Naoya Horiguchi , Dave Young On Mon, Jan 23, 2017 at 09:35:53PM +0800, Xunlei Pang wrote: > One possible timing sequence would be: > 1st kernel running on multiple cpus panicked > then the crash dump code starts > the crash dump code stops the others cpus except the crashing one > 2nd kernel boots up on the crash cpu with "nr_cpus=1" > some broadcasted mce comes on some cpu amongst the other cpus(not the crashing cpu) Where does this broadcasted MCE come from? The crash dump code triggered it? Or it happened before the panic()? Are you talking about an *actual* sequence which you're experiencing on real hw or is this something hypothetical? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply. _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec