From: Martin Steigerwald <martin@lichtvoll.de>
To: Linux kernel regressions list <regressions@lists.linux.dev>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tejun Heo <tj@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: 6.7.11: Fails to hibernate - work queues still busy
Date: Tue, 02 Apr 2024 22:03:02 +0200 [thread overview]
Message-ID: <4912750.31r3eYUQgx@lichtvoll.de> (raw)
In-Reply-To: <13486453.uLZWGnKmhe@lichtvoll.de>
Martin Steigerwald - 02.04.24, 21:29:50 CEST:
> 6.7.9 + some bcachefs upgrade/downgrade fixes included in 6.7.11 works
> okay. 6.7.11 fails. Two repeated attempts failed with a dmesg like this:
Also 6.7.11 appears not to be capable to reboot the machine. Runit says
it is rebooting and then it hangs there with no further output.
Which reminds me of:
* Re: [regression] 6.8.1: fails to hibernate with pm_runtime_force_suspend+0x0/0x120 returns -16
2024-03-16 16:02 [regression] 6.8.1: fails to hibernate with pm_runtime_force_suspend+0x0/0x120 returns -16 Martin Steigerwald
[…]
https://lore.kernel.org/regressions/22240355.EfDdHjke4D@lichtvoll.de/T/#md9dd4c2abed8503c0613d39be3cdc833aadecd6d
I don't know whether those two relate as dmesg outputs differ.
The output from 6.8.2 on hibernation attempt
[ 412.158400] port 0000:02:00.1:0.0: PM: dpm_run_callback(): pm_runtime_force_suspend+0x0/0x120 returns -16
[ 412.158418] port 0000:02:00.1:0.0: PM: failed to freeze: error -16
versus the output 6.7.11 on hibernation attempt
[ 215.764813] Showing freezable workqueues that are still busy:
[ 215.764841] workqueue events_freezable: flags=0x4
[ 215.764869] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=0 refcnt=2
[ 215.764881] inactive: pci_pme_list_scan
[ 215.764895] workqueue usb_hub_wq: flags=0x4
[ 215.764965] pwq 4: cpus=2 node=0 flags=0x0 nice=0 active=2 refcnt=3
[ 215.764974] in-flight: 350:hub_event [usbcore] hub_event [usbcore]
does not really look related to me.
Yet both kernels do not seem to like to reboot the machine.
As written I am willing to bisect this 6.7.9 versus 6.7.11 issue, but not
6.8.1 versus some 6.7 issues cause I do not want to risk filesystem
corruption on a production machine by bisecting between stable and rc1.
Best,
--
Martin
next prev parent reply other threads:[~2024-04-02 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 19:29 6.7.11: Fails to hibernate - work queues still busy Martin Steigerwald
2024-04-02 20:03 ` Martin Steigerwald [this message]
2024-04-03 4:52 ` Linux regression tracking (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:
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=4912750.31r3eYUQgx@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=gregkh@linuxfoundation.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
/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).