From: Peter Zijlstra <peterz@infradead.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/nmi: Remove the 'strange power saving mode' hint from unknown NMI handler
Date: Mon, 14 Mar 2022 11:59:00 +0100 [thread overview]
Message-ID: <Yi8f9PYNEHksy3io@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <nycvar.YFH.7.76.2203140924120.24795@cbobk.fhfr.pm>
On Mon, Mar 14, 2022 at 09:25:18AM +0100, Jiri Kosina wrote:
> From: Jiri Kosina <jkosina@suse.cz>
>
> The 'Do you have a strange power saving mode enabled?' hint when unknown
> NMI happens dates back to i386 stone age, and isn't currently really
> helpful.
>
> Unknown NMIs are coming for many different reasons (broken firmware,
> faulty hardware, ...) and rarely have anything to do with 'strange power
> saving mode' (whatever that even is).
>
> Just remove it as it's largerly misleading.
>
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Fair enough,
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> arch/x86/kernel/nmi.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/x86/kernel/nmi.c b/arch/x86/kernel/nmi.c
> index 4bce802d25fb..e73f7df362f5 100644
> --- a/arch/x86/kernel/nmi.c
> +++ b/arch/x86/kernel/nmi.c
> @@ -292,7 +292,6 @@ unknown_nmi_error(unsigned char reason, struct pt_regs *regs)
> pr_emerg("Uhhuh. NMI received for unknown reason %02x on CPU %d.\n",
> reason, smp_processor_id());
>
> - pr_emerg("Do you have a strange power saving mode enabled?\n");
> if (unknown_nmi_panic || panic_on_unrecovered_nmi)
> nmi_panic(regs, "NMI: Not continuing");
>
> --
> Jiri Kosina
> SUSE Labs
>
next prev parent reply other threads:[~2022-03-14 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 8:25 Jiri Kosina
2022-03-14 10:59 ` Peter Zijlstra [this message]
2022-03-16 10:16 ` [tip: x86/cleanups] " tip-bot2 for Jiri Kosina
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=Yi8f9PYNEHksy3io@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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®