From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"John Clemens" <clemej@gmail.com>,
"Yazen Ghannam" <Yazen.Ghannam@amd.com>,
"Tony Luck" <tony.luck@intel.com>,
linux-edac@vger.kernel.org,
"Aravind Gopalakrishnan" <aravindksg.lkml@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, "Rafał Miłecki" <rafal@milecki.pl>
Subject: x86/mce/AMD: Make sure banks were initialized before accessing them
Date: Tue, 27 Nov 2018 14:29:58 +0100 [thread overview]
Message-ID: <20181127132958.GA21840@gmail.com> (raw)
* Borislav Petkov <bp@alien8.de> wrote:
> On Tue, Nov 27, 2018 at 02:06:09PM +0100, Rafał Miłecki wrote:
> > I happen to have the same notebook with the same BIOS and the same
> > problem. So let me test it :) (see below).
>
> Even better! I might ask you do to a couple more tests if you don't
> mind. But later, once we've figured out what exactly we should do.
>
> > That's correct, with your patch I see those messages but kernel boots!
>
> Good.
>
> > Is that a valid material for a patch? If so, you can add my:
> > Tested-by: Rafał Miłecki <rafal@milecki.pl>
>
> Thanks.
>
> So yeah, I think that's small enough to be stable material.
Yeah, and note that it's also a clear and serious regression, so even if
the fix is more involved there's a justified case for fixing the bug and
marking it -stable - affected systems are crashing otherwise.
Thanks,
Ingo
next reply other threads:[~2018-11-27 13:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 13:29 Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-16 16:42 x86/mce/AMD: Make sure banks were initialized before accessing them Rafal Milecki
2019-03-07 17:08 Borislav Petkov
2019-03-07 16:55 Yazen Ghannam
2019-03-07 16:53 Borislav Petkov
2019-03-07 16:15 Yazen Ghannam
2019-03-07 14:53 Borislav Petkov
2019-03-07 12:55 Rafal Milecki
2018-12-18 19:05 Borislav Petkov
2018-12-16 22:06 Rafał Miłecki
2018-12-16 10:59 Rafał Miłecki
2018-12-16 10:33 Rafał Miłecki
2018-12-16 10:22 Borislav Petkov
2018-12-15 13:04 Rafał Miłecki
2018-11-30 10:59 Borislav Petkov
2018-11-29 14:30 Rafal Milecki
2018-11-29 13:12 Borislav Petkov
2018-11-29 8:52 Rafal Milecki
2018-11-29 8:37 Borislav Petkov
2018-11-27 16:29 Borislav Petkov
2018-11-27 15:02 Yazen Ghannam
2018-11-27 13:40 Borislav Petkov
2018-11-27 13:33 Rafal Milecki
2018-11-27 13:26 Borislav Petkov
2018-11-27 13:06 Rafał Miłecki
2018-11-27 12:38 Borislav Petkov
2018-11-27 12:09 Borislav Petkov
2018-11-27 10:17 Rafał Miłecki
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=20181127132958.GA21840@gmail.com \
--to=mingo@kernel.org \
--cc=Yazen.Ghannam@amd.com \
--cc=aravindksg.lkml@gmail.com \
--cc=bp@alien8.de \
--cc=clemej@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafal@milecki.pl \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=zajec5@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).