public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	x86@kernel.org, lkml <linux-kernel@vger.kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Stanislav Kozina <skozina@redhat.com>,
	Michael Petlan <mpetlan@redhat.com>,
	Pierre Amadio <pamadio@redhat.com>,
	onatalen@redhat.com, darcari@redhat.com
Subject: Re: unknown NMI on AMD Rome
Date: Tue, 16 Mar 2021 17:02:35 +0100	[thread overview]
Message-ID: <YFDWmwgDa/FzFsIs@angband.pl> (raw)
In-Reply-To: <YFDSSxftYw9tCGC6@krava>

On Tue, Mar 16, 2021 at 04:45:02PM +0100, Jiri Olsa wrote:
> hi,
> when running 'perf top' on AMD Rome (/proc/cpuinfo below)
> with fedora 33 kernel 5.10.22-200.fc33.x86_64
> 
> we got unknown NMI messages:
> 
> [  226.700160] Uhhuh. NMI received for unknown reason 3d on CPU 90.
> [  226.700162] Do you have a strange power saving mode enabled?
> [  226.700163] Dazed and confused, but trying to continue
> 
> also when discussing ths with Borislav, he managed to reproduce easily
> on his AMD Rome machine

Likewise, 3c on Pinnacle Ridge.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀                                       -- <willmore> on #linux-sunxi
⠈⠳⣄⠀⠀⠀⠀

  reply	other threads:[~2021-03-16 16:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 15:45 unknown NMI on AMD Rome Jiri Olsa
2021-03-16 16:02 ` Adam Borowski [this message]
2021-03-16 16:48   ` Alexander Monakov
2021-03-16 19:53 ` Peter Zijlstra
2021-03-16 20:02   ` Kim Phillips
2021-03-17  8:48     ` Ingo Molnar
2021-03-17 10:13       ` Peter Zijlstra
2021-03-17 13:32         ` Alexander Monakov
2021-03-17 13:37           ` Arnaldo Carvalho de Melo

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=YFDWmwgDa/FzFsIs@angband.pl \
    --to=kilobyte@angband.pl \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=darcari@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpetlan@redhat.com \
    --cc=onatalen@redhat.com \
    --cc=pamadio@redhat.com \
    --cc=skozina@redhat.com \
    --cc=thomas.lendacky@amd.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