linux-kernel - Re: unknown NMI on AMD Rome

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <36397980-f897-147f-df55-f37805d869c9@amd.com>
Date:   Tue, 16 Mar 2021 15:02:38 -0500
From:   Kim Phillips <kim.phillips@....com>
To:     Peter Zijlstra <peterz@...radead.org>, Jiri Olsa <jolsa@...hat.com>
Cc:     Borislav Petkov <bp@...en8.de>,
        Tom Lendacky <thomas.lendacky@....com>, x86@...nel.org,
        lkml <linux-kernel@...r.kernel.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Stanislav Kozina <skozina@...hat.com>,
        Michael Petlan <mpetlan@...hat.com>,
        Pierre Amadio <pamadio@...hat.com>, onatalen@...hat.com,
        darcari@...hat.com
Subject: Re: unknown NMI on AMD Rome

On 3/16/21 2:53 PM, Peter Zijlstra wrote:
> 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
>> [  226.769565] Uhhuh. NMI received for unknown reason 3d on CPU 84.
>> [  226.769566] Do you have a strange power saving mode enabled?
>> [  226.769567] Dazed and confused, but trying to continue
>> [  226.769771] Uhhuh. NMI received for unknown reason 2d on CPU 24.
>> [  226.769773] Do you have a strange power saving mode enabled?
>> [  226.769774] Dazed and confused, but trying to continue
>> [  226.812844] Uhhuh. NMI received for unknown reason 2d on CPU 23.
>> [  226.812846] Do you have a strange power saving mode enabled?
>> [  226.812847] Dazed and confused, but trying to continue
>> [  226.893783] Uhhuh. NMI received for unknown reason 2d on CPU 27.
>> [  226.893785] Do you have a strange power saving mode enabled?
>> [  226.893786] Dazed and confused, but trying to continue
>> [  226.900139] Uhhuh. NMI received for unknown reason 2d on CPU 40.
>> [  226.900141] Do you have a strange power saving mode enabled?
>> [  226.900143] Dazed and confused, but trying to continue
>> [  226.908763] Uhhuh. NMI received for unknown reason 3d on CPU 120.
>> [  226.908765] Do you have a strange power saving mode enabled?
>> [  226.908766] Dazed and confused, but trying to continue
>> [  227.751296] Uhhuh. NMI received for unknown reason 2d on CPU 83.
>> [  227.751298] Do you have a strange power saving mode enabled?
>> [  227.751299] Dazed and confused, but trying to continue
>> [  227.752937] Uhhuh. NMI received for unknown reason 3d on CPU 23.
>>
>> also when discussing ths with Borislav, he managed to reproduce easily
>> on his AMD Rome machine
>>
>> any idea?
> 
> Kim is the AMD point person for this I think..

Since perf top invokes precision and therefore IBS,
this looks like it's hitting erratum #1215:

https://developer.amd.com/wp-content/resources/56323-PUB_0.78.pdf

Kim