All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "Michał Pecio" <michal.pecio@gmail.com>,
	anna-maria@linutronix.de, 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 14:26:13 +0100	[thread overview]
Message-ID: <Z6n-dWDSxNCjROYV@localhost.localdomain> (raw)
In-Reply-To: <b0d55f4c-a078-42a0-a0fe-5823700f2837@molgen.mpg.de>

Le Mon, Feb 10, 2025 at 12:59:42PM +0100, Paul Menzel a écrit :
> Dear Michał,
> 
> 
> Thank you for your reply.
> 
> Am 10.02.25 um 12:45 schrieb Michał Pecio:
> 
> > > > > > > > > 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?
> 
> Unfortunately, I do not know. Right now, my logs go back until September
> 2024.
> 
>     Sep 22 13:08:04 abreu kernel: Linux version 6.11.0-07273-g1e7530883cd2
> (build@bohemianrhapsody.molgen.mpg.de) (gcc (Debian 14.2.0-5) 14.2.0, GNU ld
> (GNU Binutils for Debian) 2.43.1) #12 SMP PREEMPT_DYNAMIC Sun Sep 22
> 09:57:36 CEST 2024
> 
> > How hard to reproduce? Wasn't it during resume from hibernation?
> 
> It’s not easy to reproduce, and I believe it’s not related with resuming
> from hibernation (which I do not use) or ACPI S3 suspend. I think, I can
> force it more, when having the USB-C adapter with only the network cable
> plugged into it, and then running `sudo powertop --auto-tune`. But sometimes
> it seems unrelated.
> 
> > 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.
> 
> Interesting. Hopefully the USB folks have an idea.

Handler #08 is NET_RX. So something raised the NET_RX on some non-appropriate
place, perhaps...

Can I ask you one more trace dump?

I need:

echo 1 > /sys/kernel/tracing/events/irq/softirq_raise/enable
echo 1 > /sys/kernel/tracing/options/stacktrace

Unfortunately this will also involve a small patch:

diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index fa058510af9c..accd2eb8c927 100644
--- a/kernel/time/tick-sched.c
+++ b/kernel/time/tick-sched.c
@@ -1159,6 +1159,9 @@ static bool report_idle_softirq(void)
 	if (local_bh_blocked())
 		return false;
 
+	trace_printk("STOP\n");
+	trace_dump_stack(0);
+	tracing_off();
 	pr_warn("NOHZ tick-stop error: local softirq work is pending, handler #%02x!!!\n",
 		pending);
 	ratelimit++;



Thanks.

  reply	other threads:[~2025-02-10 13:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04  7:28 NOHZ tick-stop error: local softirq work is pending, handler #08!!! on Dell XPS 13 9360 Paul Menzel
2024-04-08 10:10 ` Anna-Maria Behnsen
2024-04-08 11:18   ` Paul Menzel
2024-04-09  7:57     ` Anna-Maria Behnsen
2024-08-21  8:20       ` 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
2025-02-10 11:59                 ` Paul Menzel
2025-02-10 13:26                   ` Frederic Weisbecker [this message]
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=Z6n-dWDSxNCjROYV@localhost.localdomain \
    --to=frederic@kernel.org \
    --cc=anna-maria@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=michal.pecio@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.