All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "ruiv.wang@gmail.com" <ruiv.wang@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"gong.chen@linux.intel.com" <gong.chen@linux.intel.com>,
	"Wang, Rui Y" <rui.y.wang@intel.com>
Subject: Re: [PATCH v3] x86/mce: Try printing all machine check banks known before panic
Date: Thu, 20 Nov 2014 11:15:05 +0100	[thread overview]
Message-ID: <20141120101505.GA791@pd.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F3294198E@ORSMSX114.amr.corp.intel.com>

On Wed, Nov 19, 2014 at 11:34:10PM +0000, Luck, Tony wrote:
> The SDM has this to say about EN=0 (in section 15.10.4.1 of volume 3B):
> 
>    When the EN flag is zero but the VAL and UC flags are one in
>    the IA32_MCi_STATUS register, the reported uncorrected error
>    in this bank is not enabled. As uncorrected errors with the
>    EN flag = 0 are not the source of machine check exceptions,
>    the MCE handler should log and clear non-enabled errors when
>    the S bit is set and should continue searching for enabled
>    errors from the other IA32_MCi_STATUS registers. Note that
>    when IA32_MCG_CAP [24] is 0, any uncorrected error condition
>    (VAL =1 and UC=1) including the one with the EN flag cleared
>    are fatal and the handler must signal the operating system to
>    reset the system. For the errors that do not generate machine
>    check exceptions, the EN flag has no meaning.
> 
> Note the "should log and clear".  We just clear ... just need to shuffle some code
> in mce.c to add the logging.

Sure, we can log those.

> But we still need something like Rui's patch - calling mcelog()
> doesn't ensure that we see something on the console about possible
> cause of the problem.

So you're saying we should drain the mcelog buffer to the console in
such situations before we panic? If so, there's drain_mcelog_buffer()
which could be changed to call print_mce() instead of going to the
x86_mce_decoder_chain.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-11-20 10:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19  9:22 [PATCH v3] x86/mce: Try printing all machine check banks known before panic ruiv.wang
2014-11-19 10:29 ` Borislav Petkov
2014-11-19 23:34   ` Luck, Tony
2014-11-20 10:15     ` Borislav Petkov [this message]
2014-11-21  1:20       ` rui wang
2014-11-21 16:41         ` Borislav Petkov
2014-11-21 17:20           ` Luck, Tony
2014-11-21 18:13             ` Borislav Petkov
2014-11-21 21:31               ` Luck, Tony
2014-11-21 21:35                 ` Borislav Petkov
2014-11-21 21:59                   ` Luck, Tony
2014-11-23 20:55                     ` Borislav Petkov
2014-11-22  2:16               ` rui wang
2014-11-22  9:44                 ` Borislav Petkov
2014-11-22 15:32                   ` rui wang
2014-11-22 16:31                     ` Borislav Petkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141120101505.GA791@pd.tnic \
    --to=bp@alien8.de \
    --cc=gong.chen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.y.wang@intel.com \
    --cc=ruiv.wang@gmail.com \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.