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@xxxxxxxxxxxx/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
