From: Thomas Gleixner <tglx@kernel.org>
To: Petr Mladek <pmladek@suse.com>, Calvin Owens <calvin@wbinvd.org>
Cc: linux-kernel@vger.kernel.org, arighi@nvidia.com,
yaozhenguo1@gmail.com, tj@kernel.org,
feng.tang@linux.alibaba.com, lirongqing@baidu.com,
realwujing@gmail.com, hu.shengming@zte.com.cn,
dianders@chromium.org, joel.granados@kernel.org,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>
Subject: Re: [BUG] Random hard lockup with userspace %ip on 7.0-rc5
Date: Wed, 25 Mar 2026 17:56:26 +0100 [thread overview]
Message-ID: <87v7ejetl1.ffs@tglx> (raw)
In-Reply-To: <acOkx9WTHPI5gnXf@pathway.suse.cz>
On Wed, Mar 25 2026 at 10:03, Petr Mladek wrote:
> Adding scheduler and NOHZ people into Cc. Hardlockup in userspace with
> interrupts enabled is strange indeed. Plus, there is some nohz-related
> function on stack...
That's a leftover from a previous syscall and ixgbe_poll is from the
most recent soft interrupt handling. Nothing to see here.
> On Tue 2026-03-24 16:32:09, Calvin Owens wrote:
>> Hi all,
>>
>> I hit the below hard lockup while building kernels a couple days ago. I
>> haven't been able to reproduce it again.
>>
>> It's clearly not actually a hard lockup, the NMI fired while %ip was in
>> userspace with irqs enabled:
Yeah. Doesn't make any sense at all. Does not ring any bell.
Thanks,
tglx
next prev parent reply other threads:[~2026-03-25 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 23:32 [BUG] Random hard lockup with userspace %ip on 7.0-rc5 Calvin Owens
2026-03-25 9:03 ` Petr Mladek
2026-03-25 16:56 ` Thomas Gleixner [this message]
2026-03-27 1:36 ` Feng Tang
2026-03-27 15:36 ` Calvin Owens
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=87v7ejetl1.ffs@tglx \
--to=tglx@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=arighi@nvidia.com \
--cc=bsegall@google.com \
--cc=calvin@wbinvd.org \
--cc=dianders@chromium.org \
--cc=dietmar.eggemann@arm.com \
--cc=feng.tang@linux.alibaba.com \
--cc=frederic@kernel.org \
--cc=hu.shengming@zte.com.cn \
--cc=joel.granados@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=realwujing@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yaozhenguo1@gmail.com \
/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