From: "Michał Pecio" <michal.pecio@gmail.com>
To: pmenzel@molgen.mpg.de
Cc: anna-maria@linutronix.de, frederic@kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, mingo@kernel.org, tglx@linutronix.de
Subject: Re: NOHZ tick-stop error: local softirq work is pending, handler #08!!! on Dell XPS 13 9360
Date: Mon, 10 Feb 2025 12:45:51 +0100 [thread overview]
Message-ID: <20250210124551.3687ae51@foxbook> (raw)
In-Reply-To: <9d056e62-4e58-40d5-9401-40d3c20c2389@molgen.mpg.de>
Hi,
>>>>>>> On Dell XPS 13 9360/0596KF, BIOS 2.21.0 06/02/2022, with Linux
>>>>>>> 6.9-rc2+
> Just for the record, I am still seeing this with 6.14.0-rc1
Is this a regression? If so, which versions were not affected?
How hard to reproduce? Wasn't it during resume from hibernation?
IRQ isuses may be a red herring, this code here is a busy wait under
spinlock. There are a few of those, they cause various problems.
if (xhci_handshake(&xhci->op_regs->status,
STS_RESTORE, 0, 100 * 1000)) {
xhci_warn(xhci, "WARN: xHC restore state timeout\n");
spin_unlock_irq(&xhci->lock);
return -ETIMEDOUT;
}
This thing timing out may be close to the root cause of everything.
Regards,
Michal
next prev parent reply other threads:[~2025-02-10 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <354a2690-9bbf-4ccb-8769-fa94707a9340@molgen.mpg.de>
[not found] ` <87o7ak411y.fsf@somnus>
[not found] ` <256fdb2e-9b83-4837-bd31-0c34e4267c31@molgen.mpg.de>
[not found] ` <87sezv7ytw.fsf@somnus>
2024-08-21 8:20 ` NOHZ tick-stop error: local softirq work is pending, handler #08!!! on Dell XPS 13 9360 Paul Menzel
2024-08-21 21:01 ` Paul Menzel
2024-10-24 12:48 ` Paul Menzel
2025-02-10 7:55 ` Paul Menzel
2025-02-10 11:45 ` Michał Pecio [this message]
2025-02-10 11:59 ` Paul Menzel
2025-02-10 13:26 ` Frederic Weisbecker
2025-02-11 11:57 ` Paul Menzel
2025-02-11 15:02 ` Frederic Weisbecker
2025-02-13 17:07 ` Paul Menzel
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=20250210124551.3687ae51@foxbook \
--to=michal.pecio@gmail.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).