archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: "" <>,
	netdev <>
Subject: Re: Fw: [Bug 215129] New: Linux kernel hangs during power down #forregzbot
Date: Sat, 4 Dec 2021 09:55:54 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Top-posting for once, to make this easy accessible to everyone.

A fix is discussed here:

#regzbot link
#regzbot monitor

Ciao, Thorsten, your Linux kernel regression tracker.

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

P.S.: I guess I'll modify regzbot to automatically catch related
discussions if they links to the same bugzilla ticket (which I forgot to
tell regzbot about when I told it about the regression), then messages
like this wouldn't be needed.

On 25.11.21 12:17, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker speaking.
> On 24.11.21 23:45, Stephen Hemminger wrote:
>> Begin forwarded message:
>> Date: Wed, 24 Nov 2021 21:14:53 +0000
>> From:
>> To:
>> Subject: [Bug 215129] New: Linux kernel hangs during power down
>>             Bug ID: 215129
>>            Summary: Linux kernel hangs during power down
>>            Product: Networking
>>            Version: 2.5
>>     Kernel Version: 5.15
>>           Hardware: All
>>                 OS: Linux
>>               Tree: Mainline
>>             Status: NEW
>>           Severity: normal
>>           Priority: P1
>>          Component: Other
>>           Assignee:
>>           Reporter:
>>         Regression: No
>> Created attachment 299703
>>   -->  
>> Kernel log after timeout occured
>> On my system the kernel is waiting for a task during shutdown which doesn't
>> complete.
>> The commit which causes this behavior is:
>> [f32a213765739f2a1db319346799f130a3d08820] ethtool: runtime-resume netdev
>> parent before ethtool ioctl ops
>> This bug causes also that the system gets unresponsive after starting Steam:
> TWIMC: To be sure this issue doesn't fall through the cracks unnoticed,
> I'm adding it to regzbot, my Linux kernel regression tracking bot:
> #regzbot ^introduced f32a213765739f2a1db319346799f130a3d08820
> #regzbot title net: kernel hangs during power down
> #regzbot ignore-activity
> Ciao, Thorsten, your Linux kernel regression tracker.
> P.S.: As a Linux kernel regression tracker I'm getting a lot of reports
> on my table. I can only look briefly into most of them. Unfortunately
> therefore I sometimes will get things wrong or miss something important.
> I hope that's not the case here; if you think it is, don't hesitate to
> tell me about it in a public reply. That's in everyone's interest, as
> what I wrote above might be misleading to everyone reading this; any
> suggestion I gave they thus might sent someone reading this down the
> wrong rabbit hole, which none of us wants.
> BTW, I have no personal interest in this issue, which is tracked using
> regzbot, my Linux kernel regression tracking bot
> ( I'm only posting
> this mail to get things rolling again and hence don't need to be CC on
> all further activities wrt to this regression.
> P.S.: If you want to know more about regzbot, check out its
> web-interface, the getting start guide, and/or the references documentation:
> The last two documents will explain how you can interact with regzbot
> yourself if your want to.
> Hint for the reporter: when reporting a regression it's in your interest
> to tell #regzbot about it in the report, as that will ensure the
> regression gets on the radar of regzbot and the regression tracker.
> That's in your interest, as they will make sure the report won't fall
> through the cracks unnoticed.
> Hint for developers: you normally don't need to care about regzbot, just
> fix the issue as you normally would. Just remember to include a 'Link:'
> tag to the report in the commit message, as explained in
> Documentation/process/submitting-patches.rst
> That aspect was recently was made more explicit in commit 1f57bd42b77c:

  reply	other threads:[~2021-12-04  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211124144505.31e15716@hermes.local>
2021-11-25 11:17 ` Fw: [Bug 215129] New: Linux kernel hangs during power down Thorsten Leemhuis
2021-12-04  8:55   ` Thorsten Leemhuis [this message]
2021-12-10  9:00     ` Fw: [Bug 215129] New: Linux kernel hangs during power down #forregzbot Thorsten Leemhuis
2021-12-23 19:09     ` Thorsten Leemhuis

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: Fw: [Bug 215129] New: Linux kernel hangs during power down #forregzbot' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).