From: Thomas Gleixner <tglx@linutronix.de>
To: "Laurențiu Nicola" <lnicola@dend.ro>
Cc: mingo@kernel.org, bp@alien8.de, x86@kernel.org,
trivial@kernel.org, LKML <linux-kernel@vger.kernel.org>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH] x86/irq: Lower unhandled irq error severity
Date: Tue, 01 Dec 2020 00:34:41 +0100 [thread overview]
Message-ID: <87tut6h10u.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <96085c8a-b144-4fd3-b1fb-45763b5b64a4@www.fastmail.com>
On Mon, Nov 30 2020 at 19:22, Laurențiu Nicola wrote:
> On Mon, Nov 30, 2020, at 18:56, Thomas Gleixner wrote:
>> > That's right, sorry. It still boots, but it's no longer "quiet",
>> > that's what I meant.
>>
>> Right, but surpressing that is not a solution.
>
> I'm just downgrading it from "emergency" to "error". It will still be
> displayed for most users snd anyone looking in dmesg. But I'm unlikely
> to convince my motherboard manufacturer to fix this in the BIOS, and
> the errors are basically unactionable and uninformative (unlike say
> "can't set up page mappings" or "your CPU might be on fire" which
> would really imply a crash soon).
The point is that for some cases this can result in a non working
machine which just hangs and if it's below the usual loglevel cutoff,
then it's not visible, which is more annoying than a non-quiet boot if
you're affected.
We are looking into a way to mitigate that AMD wreckage, but so far we
don't even know where exactly this comes from. The reason why we are
pretty sure that it is a BIOS/Firmware issue is that some people
reported it to be gone after a BIOS update and quite some machines do
not have this issue at all.
Just for completeness sake. Can you provide the line in /proc/interrupts
for irq 7 on that machine?
Thanks,
tglx
next prev parent reply other threads:[~2020-11-30 23:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201126074734.12664-1-lnicola@dend.ro>
2020-11-27 0:12 ` [PATCH] x86/irq: Lower unhandled irq error severity Thomas Gleixner
2020-11-27 8:03 ` Laurențiu Nicola
2020-11-30 16:56 ` Thomas Gleixner
2020-11-30 17:22 ` Laurențiu Nicola
2020-11-30 23:34 ` Thomas Gleixner [this message]
2020-12-01 8:18 ` Laurențiu Nicola
2020-12-01 10:38 ` Thomas Gleixner
2020-12-01 10:41 ` Laurențiu Nicola
2020-12-01 14:36 ` Tom Lendacky
2020-12-01 14:44 ` Laurențiu Nicola
2020-12-01 17:05 ` Tom Lendacky
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=87tut6h10u.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lnicola@dend.ro \
--cc=mingo@kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=trivial@kernel.org \
--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