From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
acme@kernel.org, linux-perf-users@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: NMI reason 2d when running perf
Date: Sat, 18 Mar 2023 14:44:14 +0000 [thread overview]
Message-ID: <ZBXOPvIqybwtihJY@gallifrey> (raw)
In-Reply-To: <25fccb43-8338-a690-0009-384dc0640169@kernel.dk>
* Jens Axboe (axboe@kernel.dk) wrote:
> Hi,
>
> When running perf on my Dell R7525 on a running process, I get a ton of:
>
> [ 504.234782] Dazed and confused, but trying to continue
> [ 504.267843] Uhhuh. NMI received for unknown reason 2d on CPU 48.
> [ 504.267846] Dazed and confused, but trying to continue
> [ 504.335975] Uhhuh. NMI received for unknown reason 2d on CPU 48.
> [ 504.335977] Dazed and confused, but trying to continue
> [ 504.368031] Uhhuh. NMI received for unknown reason 2d on CPU 48.
> [ 504.368033] Dazed and confused, but trying to continue
> [ 504.371037] Uhhuh. NMI received for unknown reason 2d on CPU 48.
> [ 504.371038] Dazed and confused, but trying to continue
> [ 504.439165] Uhhuh. NMI received for unknown reason 2d on CPU 48.
> [ 504.439167] Dazed and confused, but trying to continue
>
> spew in dmesg. The box has 2x7763 CPUS. This seems to be a recent
> regression, been using this box for a while and haven't seen this
> before. The test being traced is pinned to CPU 48. The box is currently
> running:
I'm not sure this is new; I've seen this intermittently on AMD boxes
for a few years. Always when running perf or related tools.
Dave
> commit 6015b1aca1a233379625385feb01dd014aca60b5 (origin/master, origin/HEAD)
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Tue Mar 14 19:32:38 2023 -0700
>
> sched_getaffinity: don't assume 'cpumask_size()' is fully initialized
>
> with the pending block/io_uring branches merged in for testing.
>
> --
> Jens Axboe
>
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2023-03-18 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 14:25 Jens Axboe
2023-03-18 14:44 ` Dr. David Alan Gilbert [this message]
2023-03-20 4:44 ` Ravi Bangoria
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=ZBXOPvIqybwtihJY@gallifrey \
--to=linux@treblig.org \
--cc=acme@kernel.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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®