* Fw: [Bug 215129] New: Linux kernel hangs during power down
@ 2021-11-24 22:45 Stephen Hemminger
2021-11-25 0:46 ` Jakub Kicinski
2021-11-25 11:17 ` Fw: " Thorsten Leemhuis
0 siblings, 2 replies; 9+ messages in thread
From: Stephen Hemminger @ 2021-11-24 22:45 UTC (permalink / raw)
To: netdev
Begin forwarded message:
Date: Wed, 24 Nov 2021 21:14:53 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 215129] New: Linux kernel hangs during power down
https://bugzilla.kernel.org/show_bug.cgi?id=215129
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: stephen@networkplumber.org
Reporter: martin.stolpe@gmail.com
Regression: No
Created attachment 299703
--> https://bugzilla.kernel.org/attachment.cgi?id=299703&action=edit
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:
https://steamcommunity.com/app/221410/discussions/2/3194736442566303600/
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [Bug 215129] New: Linux kernel hangs during power down 2021-11-24 22:45 Fw: [Bug 215129] New: Linux kernel hangs during power down Stephen Hemminger @ 2021-11-25 0:46 ` Jakub Kicinski 2021-11-25 7:32 ` Heiner Kallweit 2021-11-25 11:17 ` Fw: " Thorsten Leemhuis 1 sibling, 1 reply; 9+ messages in thread From: Jakub Kicinski @ 2021-11-25 0:46 UTC (permalink / raw) To: Stephen Hemminger; +Cc: netdev, ath10k, Heiner Kallweit, Kalle Valo Adding Kalle and Hainer. On Wed, 24 Nov 2021 14:45:05 -0800 Stephen Hemminger wrote: > Begin forwarded message: > > Date: Wed, 24 Nov 2021 21:14:53 +0000 > From: bugzilla-daemon@bugzilla.kernel.org > To: stephen@networkplumber.org > Subject: [Bug 215129] New: Linux kernel hangs during power down > > > https://bugzilla.kernel.org/show_bug.cgi?id=215129 > > 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: stephen@networkplumber.org > Reporter: martin.stolpe@gmail.com > Regression: No > > Created attachment 299703 > --> https://bugzilla.kernel.org/attachment.cgi?id=299703&action=edit > 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: > https://steamcommunity.com/app/221410/discussions/2/3194736442566303600/ > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Bug 215129] New: Linux kernel hangs during power down 2021-11-25 0:46 ` Jakub Kicinski @ 2021-11-25 7:32 ` Heiner Kallweit 2021-11-25 15:49 ` Jakub Kicinski 2021-11-25 21:11 ` Heiner Kallweit 0 siblings, 2 replies; 9+ messages in thread From: Heiner Kallweit @ 2021-11-25 7:32 UTC (permalink / raw) To: Jakub Kicinski, Jesse Brandeburg, Tony Nguyen, intel-wired-lan, Kalle Valo Cc: netdev, ath10k, Stephen Hemminger On 25.11.2021 01:46, Jakub Kicinski wrote: > Adding Kalle and Hainer. > > On Wed, 24 Nov 2021 14:45:05 -0800 Stephen Hemminger wrote: >> Begin forwarded message: >> >> Date: Wed, 24 Nov 2021 21:14:53 +0000 >> From: bugzilla-daemon@bugzilla.kernel.org >> To: stephen@networkplumber.org >> Subject: [Bug 215129] New: Linux kernel hangs during power down >> >> >> https://bugzilla.kernel.org/show_bug.cgi?id=215129 >> >> 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: stephen@networkplumber.org >> Reporter: martin.stolpe@gmail.com >> Regression: No >> >> Created attachment 299703 >> --> https://bugzilla.kernel.org/attachment.cgi?id=299703&action=edit >> 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: >> https://steamcommunity.com/app/221410/discussions/2/3194736442566303600/ >> > I think the reference to ath10k_pci is misleading, Kalle isn't needed here. The actual issue is a RTNL deadlock in igb_resume(). See log snippet: Nov 24 18:56:19 MartinsPc kernel: igb_resume+0xff/0x1e0 [igb 21bf6a00cb1f20e9b0e8434f7f8748a0504e93f8] Nov 24 18:56:19 MartinsPc kernel: pci_pm_runtime_resume+0xa7/0xd0 Nov 24 18:56:19 MartinsPc kernel: ? pci_pm_freeze_noirq+0x110/0x110 Nov 24 18:56:19 MartinsPc kernel: __rpm_callback+0x41/0x120 Nov 24 18:56:19 MartinsPc kernel: ? pci_pm_freeze_noirq+0x110/0x110 Nov 24 18:56:19 MartinsPc kernel: rpm_callback+0x35/0x70 Nov 24 18:56:19 MartinsPc kernel: rpm_resume+0x567/0x810 Nov 24 18:56:19 MartinsPc kernel: __pm_runtime_resume+0x4a/0x80 Nov 24 18:56:19 MartinsPc kernel: dev_ethtool+0xd4/0x2d80 We have at least two places in net core where runtime_resume() is called under RTNL. This conflicts with the current structure in few Intel drivers that have something like the following in their resume path. rtnl_lock(); if (!err && netif_running(netdev)) err = __igb_open(netdev, true); if (!err) netif_device_attach(netdev); rtnl_unlock(); Other drivers don't do this, so it's the question whether it's actually needed here to take RTNL. Some discussion was started [0], but it ended w/o tangible result and since then it has been surprisingly quiet. [0] https://www.spinics.net/lists/netdev/msg736880.html ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Bug 215129] New: Linux kernel hangs during power down 2021-11-25 7:32 ` Heiner Kallweit @ 2021-11-25 15:49 ` Jakub Kicinski 2021-11-25 21:11 ` Heiner Kallweit 1 sibling, 0 replies; 9+ messages in thread From: Jakub Kicinski @ 2021-11-25 15:49 UTC (permalink / raw) To: Heiner Kallweit Cc: Jesse Brandeburg, Tony Nguyen, intel-wired-lan, netdev, ath10k, Stephen Hemminger On Thu, 25 Nov 2021 08:32:18 +0100 Heiner Kallweit wrote: > I think the reference to ath10k_pci is misleading, Kalle isn't needed here. > The actual issue is a RTNL deadlock in igb_resume(). See log snippet: > > Nov 24 18:56:19 MartinsPc kernel: igb_resume+0xff/0x1e0 [igb 21bf6a00cb1f20e9b0e8434f7f8748a0504e93f8] > Nov 24 18:56:19 MartinsPc kernel: pci_pm_runtime_resume+0xa7/0xd0 > Nov 24 18:56:19 MartinsPc kernel: ? pci_pm_freeze_noirq+0x110/0x110 > Nov 24 18:56:19 MartinsPc kernel: __rpm_callback+0x41/0x120 > Nov 24 18:56:19 MartinsPc kernel: ? pci_pm_freeze_noirq+0x110/0x110 > Nov 24 18:56:19 MartinsPc kernel: rpm_callback+0x35/0x70 > Nov 24 18:56:19 MartinsPc kernel: rpm_resume+0x567/0x810 > Nov 24 18:56:19 MartinsPc kernel: __pm_runtime_resume+0x4a/0x80 > Nov 24 18:56:19 MartinsPc kernel: dev_ethtool+0xd4/0x2d80 > > We have at least two places in net core where runtime_resume() is called > under RTNL. This conflicts with the current structure in few Intel drivers > that have something like the following in their resume path. > > rtnl_lock(); > if (!err && netif_running(netdev)) > err = __igb_open(netdev, true); > > if (!err) > netif_device_attach(netdev); > rtnl_unlock(); > > Other drivers don't do this, so it's the question whether it's actually > needed here to take RTNL. Some discussion was started [0], but it ended > w/o tangible result and since then it has been surprisingly quiet. > > [0] https://www.spinics.net/lists/netdev/msg736880.html Ah, that makes perfect sense, I didn't see that stack trace. Dropping Kalle from CC. Let's hear what Intel folks have to say.. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Bug 215129] New: Linux kernel hangs during power down 2021-11-25 7:32 ` Heiner Kallweit 2021-11-25 15:49 ` Jakub Kicinski @ 2021-11-25 21:11 ` Heiner Kallweit 2021-11-26 7:55 ` Fwd: " Heiner Kallweit 1 sibling, 1 reply; 9+ messages in thread From: Heiner Kallweit @ 2021-11-25 21:11 UTC (permalink / raw) To: Jakub Kicinski, Jesse Brandeburg, Tony Nguyen, intel-wired-lan, Kalle Valo Cc: netdev, ath10k, Stephen Hemminger On 25.11.2021 08:32, Heiner Kallweit wrote: > On 25.11.2021 01:46, Jakub Kicinski wrote: >> Adding Kalle and Hainer. >> >> On Wed, 24 Nov 2021 14:45:05 -0800 Stephen Hemminger wrote: >>> Begin forwarded message: >>> >>> Date: Wed, 24 Nov 2021 21:14:53 +0000 >>> From: bugzilla-daemon@bugzilla.kernel.org >>> To: stephen@networkplumber.org >>> Subject: [Bug 215129] New: Linux kernel hangs during power down >>> >>> >>> https://bugzilla.kernel.org/show_bug.cgi?id=215129 >>> >>> 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: stephen@networkplumber.org >>> Reporter: martin.stolpe@gmail.com >>> Regression: No >>> >>> Created attachment 299703 >>> --> https://bugzilla.kernel.org/attachment.cgi?id=299703&action=edit >>> 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: >>> https://steamcommunity.com/app/221410/discussions/2/3194736442566303600/ >>> >> > > I think the reference to ath10k_pci is misleading, Kalle isn't needed here. > The actual issue is a RTNL deadlock in igb_resume(). See log snippet: > > Nov 24 18:56:19 MartinsPc kernel: igb_resume+0xff/0x1e0 [igb 21bf6a00cb1f20e9b0e8434f7f8748a0504e93f8] > Nov 24 18:56:19 MartinsPc kernel: pci_pm_runtime_resume+0xa7/0xd0 > Nov 24 18:56:19 MartinsPc kernel: ? pci_pm_freeze_noirq+0x110/0x110 > Nov 24 18:56:19 MartinsPc kernel: __rpm_callback+0x41/0x120 > Nov 24 18:56:19 MartinsPc kernel: ? pci_pm_freeze_noirq+0x110/0x110 > Nov 24 18:56:19 MartinsPc kernel: rpm_callback+0x35/0x70 > Nov 24 18:56:19 MartinsPc kernel: rpm_resume+0x567/0x810 > Nov 24 18:56:19 MartinsPc kernel: __pm_runtime_resume+0x4a/0x80 > Nov 24 18:56:19 MartinsPc kernel: dev_ethtool+0xd4/0x2d80 > > We have at least two places in net core where runtime_resume() is called > under RTNL. This conflicts with the current structure in few Intel drivers > that have something like the following in their resume path. > > rtnl_lock(); > if (!err && netif_running(netdev)) > err = __igb_open(netdev, true); > > if (!err) > netif_device_attach(netdev); > rtnl_unlock(); > > Other drivers don't do this, so it's the question whether it's actually > needed here to take RTNL. Some discussion was started [0], but it ended > w/o tangible result and since then it has been surprisingly quiet. > > [0] https://www.spinics.net/lists/netdev/msg736880.html > I think the problem with runtime_resume() taking RTNL could also hit the driver internally. See following call chain: If this would ever be called when the device is runtime-suspended, then a similar deadlock would occur. __dev_open() - called with RTNL held igb_open() __igb_open() - arg resuming is false if (!resuming) pm_runtime_get_sync(&pdev->dev); igb_resume() rtnl_lock() ^ permalink raw reply [flat|nested] 9+ messages in thread
* Fwd: [Bug 215129] New: Linux kernel hangs during power down 2021-11-25 21:11 ` Heiner Kallweit @ 2021-11-26 7:55 ` Heiner Kallweit 0 siblings, 0 replies; 9+ messages in thread From: Heiner Kallweit @ 2021-11-26 7:55 UTC (permalink / raw) To: Vinicius Costa Gomes; +Cc: netdev, Jakub Kicinski FYI That's what Jakub was just referring to. -------- Forwarded Message -------- Subject: Re: [Bug 215129] New: Linux kernel hangs during power down Date: Thu, 25 Nov 2021 22:11:16 +0100 From: Heiner Kallweit <hkallweit1@gmail.com> To: Jakub Kicinski <kuba@kernel.org>, Jesse Brandeburg <jesse.brandeburg@intel.com>, Tony Nguyen <anthony.l.nguyen@intel.com>, intel-wired-lan <intel-wired-lan@lists.osuosl.org>, Kalle Valo <kvalo@codeaurora.org> CC: netdev@vger.kernel.org, ath10k@lists.infradead.org, Stephen Hemminger <stephen@networkplumber.org> On 25.11.2021 08:32, Heiner Kallweit wrote: > On 25.11.2021 01:46, Jakub Kicinski wrote: >> Adding Kalle and Hainer. >> >> On Wed, 24 Nov 2021 14:45:05 -0800 Stephen Hemminger wrote: >>> Begin forwarded message: >>> >>> Date: Wed, 24 Nov 2021 21:14:53 +0000 >>> From: bugzilla-daemon@bugzilla.kernel.org >>> To: stephen@networkplumber.org >>> Subject: [Bug 215129] New: Linux kernel hangs during power down >>> >>> >>> https://bugzilla.kernel.org/show_bug.cgi?id=215129 >>> >>> 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: stephen@networkplumber.org >>> Reporter: martin.stolpe@gmail.com >>> Regression: No >>> >>> Created attachment 299703 >>> --> https://bugzilla.kernel.org/attachment.cgi?id=299703&action=edit >>> 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: >>> https://steamcommunity.com/app/221410/discussions/2/3194736442566303600/ >>> >> > > I think the reference to ath10k_pci is misleading, Kalle isn't needed here. > The actual issue is a RTNL deadlock in igb_resume(). See log snippet: > > Nov 24 18:56:19 MartinsPc kernel: igb_resume+0xff/0x1e0 [igb 21bf6a00cb1f20e9b0e8434f7f8748a0504e93f8] > Nov 24 18:56:19 MartinsPc kernel: pci_pm_runtime_resume+0xa7/0xd0 > Nov 24 18:56:19 MartinsPc kernel: ? pci_pm_freeze_noirq+0x110/0x110 > Nov 24 18:56:19 MartinsPc kernel: __rpm_callback+0x41/0x120 > Nov 24 18:56:19 MartinsPc kernel: ? pci_pm_freeze_noirq+0x110/0x110 > Nov 24 18:56:19 MartinsPc kernel: rpm_callback+0x35/0x70 > Nov 24 18:56:19 MartinsPc kernel: rpm_resume+0x567/0x810 > Nov 24 18:56:19 MartinsPc kernel: __pm_runtime_resume+0x4a/0x80 > Nov 24 18:56:19 MartinsPc kernel: dev_ethtool+0xd4/0x2d80 > > We have at least two places in net core where runtime_resume() is called > under RTNL. This conflicts with the current structure in few Intel drivers > that have something like the following in their resume path. > > rtnl_lock(); > if (!err && netif_running(netdev)) > err = __igb_open(netdev, true); > > if (!err) > netif_device_attach(netdev); > rtnl_unlock(); > > Other drivers don't do this, so it's the question whether it's actually > needed here to take RTNL. Some discussion was started [0], but it ended > w/o tangible result and since then it has been surprisingly quiet. > > [0] https://www.spinics.net/lists/netdev/msg736880.html > I think the problem with runtime_resume() taking RTNL could also hit the driver internally. See following call chain: If this would ever be called when the device is runtime-suspended, then a similar deadlock would occur. __dev_open() - called with RTNL held igb_open() __igb_open() - arg resuming is false if (!resuming) pm_runtime_get_sync(&pdev->dev); igb_resume() rtnl_lock() ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Fw: [Bug 215129] New: Linux kernel hangs during power down 2021-11-24 22:45 Fw: [Bug 215129] New: Linux kernel hangs during power down Stephen Hemminger 2021-11-25 0:46 ` Jakub Kicinski @ 2021-11-25 11:17 ` Thorsten Leemhuis 2021-12-04 8:55 ` Fw: [Bug 215129] New: Linux kernel hangs during power down #forregzbot Thorsten Leemhuis 1 sibling, 1 reply; 9+ messages in thread From: Thorsten Leemhuis @ 2021-11-25 11:17 UTC (permalink / raw) To: regressions, netdev 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: bugzilla-daemon@bugzilla.kernel.org > To: stephen@networkplumber.org > Subject: [Bug 215129] New: Linux kernel hangs during power down > > > https://bugzilla.kernel.org/show_bug.cgi?id=215129 > > 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: stephen@networkplumber.org > Reporter: martin.stolpe@gmail.com > Regression: No > > Created attachment 299703 > --> https://bugzilla.kernel.org/attachment.cgi?id=299703&action=edit > 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: > https://steamcommunity.com/app/221410/discussions/2/3194736442566303600/ 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 (https://linux-regtracking.leemhuis.info/regzbot/). 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: https://linux-regtracking.leemhuis.info/regzbot/ https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md 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: https://git.kernel.org/linus/1f57bd42b77c ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Fw: [Bug 215129] New: Linux kernel hangs during power down #forregzbot 2021-11-25 11:17 ` Fw: " Thorsten Leemhuis @ 2021-12-04 8:55 ` Thorsten Leemhuis 2021-12-10 9:00 ` Thorsten Leemhuis 0 siblings, 1 reply; 9+ messages in thread From: Thorsten Leemhuis @ 2021-12-04 8:55 UTC (permalink / raw) To: regressions, netdev Top-posting for once, to make this easy accessible to everyone. A fix is discussed here: #regzbot link https://bugzilla.kernel.org/show_bug.cgi?id=215129 #regzbot monitor https://lore.kernel.org/all/6bb28d2f-4884-7696-0582-c26c35534bae@gmail.com/ 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: bugzilla-daemon@bugzilla.kernel.org >> To: stephen@networkplumber.org >> Subject: [Bug 215129] New: Linux kernel hangs during power down >> >> >> https://bugzilla.kernel.org/show_bug.cgi?id=215129 >> >> 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: stephen@networkplumber.org >> Reporter: martin.stolpe@gmail.com >> Regression: No >> >> Created attachment 299703 >> --> https://bugzilla.kernel.org/attachment.cgi?id=299703&action=edit >> 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: >> https://steamcommunity.com/app/221410/discussions/2/3194736442566303600/ > > 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 > (https://linux-regtracking.leemhuis.info/regzbot/). 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: > > https://linux-regtracking.leemhuis.info/regzbot/ > https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md > https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md > > 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: > https://git.kernel.org/linus/1f57bd42b77c > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Fw: [Bug 215129] New: Linux kernel hangs during power down #forregzbot 2021-12-04 8:55 ` Fw: [Bug 215129] New: Linux kernel hangs during power down #forregzbot Thorsten Leemhuis @ 2021-12-10 9:00 ` Thorsten Leemhuis 0 siblings, 0 replies; 9+ messages in thread From: Thorsten Leemhuis @ 2021-12-10 9:00 UTC (permalink / raw) To: regressions, netdev Hi, this is your Linux kernel regression tracker speaking. On 04.12.21 09:55, Thorsten Leemhuis wrote: > Top-posting for once, to make this easy accessible to everyone. Once again. The fix sadly didn't link to the mail with the report on the list, as it should (see https://git.kernel.org/linus/1f57bd42b77c ), otherwise this message wouldn't be needed. But whatever, for the record & regzbot: A fix was committed here: https://kernel.googlesource.com/pub/scm/linux/kernel/git/tnguy/net-queue/+/de98e3651464acb08a5bba6df9ad323c7e9cdc33 Not yet in next and the commit-id is likely to different later, but I ignore that for now and tell regzbot about it nevertheless: #regzbot fixed-by: de98e3651464acb08a5bba6df9ad323c7e9cdc33 Ciao, Thorsten > A fix is discussed here: > > #regzbot link https://bugzilla.kernel.org/show_bug.cgi?id=215129 > #regzbot monitor > https://lore.kernel.org/all/6bb28d2f-4884-7696-0582-c26c35534bae@gmail.com/ > > 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: bugzilla-daemon@bugzilla.kernel.org >>> To: stephen@networkplumber.org >>> Subject: [Bug 215129] New: Linux kernel hangs during power down >>> >>> >>> https://bugzilla.kernel.org/show_bug.cgi?id=215129 >>> >>> 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: stephen@networkplumber.org >>> Reporter: martin.stolpe@gmail.com >>> Regression: No >>> >>> Created attachment 299703 >>> --> https://bugzilla.kernel.org/attachment.cgi?id=299703&action=edit >>> 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: >>> https://steamcommunity.com/app/221410/discussions/2/3194736442566303600/ >> >> 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 >> (https://linux-regtracking.leemhuis.info/regzbot/). 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: >> >> https://linux-regtracking.leemhuis.info/regzbot/ >> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md >> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md >> >> 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: >> https://git.kernel.org/linus/1f57bd42b77c >> ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2021-12-10 9:00 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-11-24 22:45 Fw: [Bug 215129] New: Linux kernel hangs during power down Stephen Hemminger 2021-11-25 0:46 ` Jakub Kicinski 2021-11-25 7:32 ` Heiner Kallweit 2021-11-25 15:49 ` Jakub Kicinski 2021-11-25 21:11 ` Heiner Kallweit 2021-11-26 7:55 ` Fwd: " Heiner Kallweit 2021-11-25 11:17 ` Fw: " Thorsten Leemhuis 2021-12-04 8:55 ` Fw: [Bug 215129] New: Linux kernel hangs during power down #forregzbot Thorsten Leemhuis 2021-12-10 9:00 ` Thorsten Leemhuis
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).