From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>,
Thomas Gleixner <tglx@linutronix.de>,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
linux-edac@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg
Date: Mon, 21 May 2018 22:19:14 +0200 [thread overview]
Message-ID: <20180521201914.GB14289@pd.tnic> (raw)
In-Reply-To: <20180521165803.GA15717@agluck-desk>
On Mon, May 21, 2018 at 09:58:03AM -0700, Luck, Tony wrote:
> So BIOS did something to trigger some issues in the L3
> cache (more than once since the overflow and filter bits
> are both set).
>
> I think (but am not 100% sure because I don't have an
> internal decoder that knows about this specific CPU model)
> that the error was a write-back to MMIO (this matches other
> cases where we've seen BIOS trigger some error and left the
> logs for Linux to find at boot).
We do have that __mcheck_cpu_apply_quirks() and cfg->bootlog thing to
shut it up. Because it all sounds like BIOS forgot to clean up after
itself and the kernel seeing those errors is doing nothing but puzzle
people.
And it's not like there's anything we can do about the erros...
Anyway, just thinking out loud.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
prev parent reply other threads:[~2018-05-21 20:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 15:49 Jeffrin Thalakkottoor
2018-05-14 16:27 ` Borislav Petkov
2018-05-14 16:50 ` Luck, Tony
2018-05-20 11:00 ` Jeffrin Thalakkottoor
2018-05-20 11:57 ` Jeffrin Thalakkottoor
2018-05-20 20:40 ` Borislav Petkov
2018-05-21 12:01 ` Jeffrin Thalakkottoor
2018-05-21 16:58 ` Luck, Tony
2018-05-21 20:11 ` Jeffrin Thalakkottoor
2018-05-21 20:57 ` Luck, Tony
2018-05-21 21:13 ` Jeffrin Thalakkottoor
2018-05-22 0:06 ` Luck, Tony
2018-05-22 8:34 ` Borislav Petkov
2018-05-22 13:16 ` Jeffrin Thalakkottoor
2018-05-21 20:19 ` 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=20180521201914.GB14289@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jeffrin@rajagiritech.edu.in \
--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
all inboxes | Powered by JetHome®