From: Anna-Maria Behnsen <anna-maria@linutronix.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Frederic Weisbecker <frederic@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: NOHZ tick-stop error: local softirq work is pending, handler #08!!! on Dell XPS 13 9360
Date: Tue, 09 Apr 2024 09:57:31 +0200 [thread overview]
Message-ID: <87sezv7ytw.fsf@somnus> (raw)
In-Reply-To: <256fdb2e-9b83-4837-bd31-0c34e4267c31@molgen.mpg.de>
Paul Menzel <pmenzel@molgen.mpg.de> writes:
> Dear Anna-Maria,
>
>
> Thank you for your response.
>
>
> Am 08.04.24 um 12:10 schrieb Anna-Maria Behnsen:
>
>> Paul Menzel writes:
>
>>> On Dell XPS 13 9360/0596KF, BIOS 2.21.0 06/02/2022, with Linux 6.9-rc2+
>>> built from commit b1e6ec0a0fd0 (Merge tag 'docs-6.9-fixes' of
>>> git://git.lwn.net/linux) the external USB-C adapter Dell DA300 stopped
>>> working (only the Ethernet port was used). Linux logged:
>>
>> thanks for the report. Can you please provide a trace beside the dmesg
>> output? The following trace events should be enabled (via kernel command
>> line):
>>
>> trace_event=timer:*,timer_migration:*,sched:sched_switch,sched:sched_wakeup,sched:sched_process_hang,irq:softirq_entry,irq:softirq_raise,irq:softirq_exit
> Unfortunately I haven’t been able to reproduce it until now. Should it
> happen again, I am going to try your suggestion.
>
Thanks for letting me know.
Thanks,
Anna-Maria
next prev parent reply other threads:[~2024-04-09 7:57 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 [this message]
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
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=87sezv7ytw.fsf@somnus \
--to=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-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).