The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
Cc: tony.luck@intel.com, mingo@redhat.com, tglx@linutronix.de,
	hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org,
	linux-edac@vger.kernel.org
Subject: Re: [PATCH V2] x86, mce, amd: Enable interrupts by default if HW capable
Date: Fri, 6 Feb 2015 17:38:37 +0100	[thread overview]
Message-ID: <20150206163837.GI3220@pd.tnic> (raw)
In-Reply-To: <1422896561-7695-1-git-send-email-aravind.gopalakrishnan@amd.com>

On Mon, Feb 02, 2015 at 11:02:41AM -0600, Aravind Gopalakrishnan wrote:
> We setup APIC vectors for threshold errors if interrupt_capable.
> However, we don't set interrupt_enable by default.
> Re-working threshold_restart_bank() here so that the first time we
> set up lvt_offset, we also set IntType to APIC.
> 
> User is still allowed to disable interrupts through sysfs.
> 
> While at it, check if status is valid before we proceed to log
> error using mce_log. This is because, in multi-node platforms,
> only NBC has valid status info. So, the decoding of status values
> on the non-NBC leads to noise on kernel logs like so-
> 
> [  440.509744] EDAC DEBUG: amd64_inject_write_store: section=0x80000000
> word_bits=0x10020001
> [  466.570925] [Hardware Error]: Corrected error, no action required.
> [  466.570935] [Hardware Error]: CPU:25 (15:2:0) MC4_STATUS[-|CE|-|-|-
> [  466.570936] [Hardware Error]: Corrected error, no action required.
> [  466.570959] [Hardware Error]: CPU:26 (15:2:0) MC4_STATUS[-|CE|-|-|-
> <...>
> [  466.571293] WARNING: CPU: 25 PID: 0 at drivers/edac/amd64_edac.c:2147
> decode_bus_error+0x1ba/0x2a0()
> [  466.571301] WARNING: CPU: 26 PID: 0 at drivers/edac/amd64_edac.c:2147
> decode_bus_error+0x1ba/0x2a0()
> [  466.571303] Something is rotten in the state of Denmark.
> 
> Suggested-by: Borislav Petkov <bp@suse.de>
> Signed-off-by: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>

Queued for 3.21, thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

      reply	other threads:[~2015-02-06 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 17:02 [PATCH V2] x86, mce, amd: Enable interrupts by default if HW capable Aravind Gopalakrishnan
2015-02-06 16:38 ` Borislav Petkov [this message]

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=20150206163837.GI3220@pd.tnic \
    --to=bp@alien8.de \
    --cc=aravind.gopalakrishnan@amd.com \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox