Bug 2393381 - Kernel 6.16.3 breaks suspend/reboot/poweroff
Summary: Kernel 6.16.3 breaks suspend/reboot/poweroff
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 42
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-04 21:48 UTC by Alexandra
Modified: 2025-10-09 11:01 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
kernel.log (146.61 KB, text/plain)
2025-09-04 21:48 UTC, Alexandra
no flags Details

Description Alexandra 2025-09-04 21:48:02 UTC
Created attachment 2105749 [details]
kernel.log

1. Please describe the problem:
   Kernel 6.16.3 breaks suspend/reboot/poweroff

2. What is the Version-Release number of the kernel: 6.16.3

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
   6.16.3, works with out issue in 6.15.9


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
   Boot to 6.16.3 → test systemctl suspend → fails instantly.

   Test sudo reboot → hangs.

   Boot older kernel (6.15.9) → tests succeed.


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
   Did not test with that.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
   NVIDIA 

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 geoffrey.ferrari 2025-09-09 08:46:48 UTC
Same issue here and still not working with kernel-6.16.4-200.fc42.x86_64.

Comment 2 Ambrogio 2025-09-20 13:45:03 UTC
Same issue here.
Starting from 6.16.3 the shutdown doesn't do the poweroff.

It seems all ok, but the only way to poweroff the laptop is to push power button for a long time.

Last try with 6.16.7-200.fc42.x86_64 - same effect.

This is my machine type:

# inxi -M
Machine:
  Type: Laptop System: Dell product: Latitude 7650 v: N/A serial: BXXCZ64
  Mobo: Dell model: 0XR3XW v: A00 serial: /BXXCZ64/CNCMK004BG0565/
    UEFI: Dell v: 1.15.1 date: 07/01/2025

I seen some other bugs with same problem.
Someone says to use noapic (not tested by me) or to wait some minutes (also not tested).

https://bugzilla.redhat.com/show_bug.cgi?id=2389012
https://bugzilla.redhat.com/show_bug.cgi?id=2392115
https://bugzilla.redhat.com/show_bug.cgi?id=2392116

Comment 3 POE 2025-09-26 05:39:17 UTC
Came here to say I also experience this after upgrading. I can't say for sure that this is a kernel issue
but I was upgrading my kernel because I wanted to test the v4l loopback module (which I am not currently using)

My latest upgrade brought me to: 6.16.8-200.fc42.x86_64 but I also had ussues with  6.16.7. 
(I am not sure before that, but my upgrade logs seems to suggest 16.5ish was working for me)

MachineType: Dell XPS 13 9340, UEFI: Dell v: 1.19.0 date: 08/07/2025

If I quickly press Esc after poweroff I can see nothing unusual and there is nothing in the log. 

At one occasion I could see

Sep 24 17:42:27 X.local kernel: watchdog: watchdog0: watchdog did not stop!
Sep 24 17:42:27 X.local systemd[1]: Using hardware watchdog 'iTCO_wdt', version 6, device /dev/watchdog0
Sep 24 17:42:27 X.local systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 6, device /dev/watchdog0

but I think this is a red herring. 

Kernel modules that I have installed 
kmod-intel-ipu6-6.16.8-200.fc42
kmod-v4l2loopback-6.16.8-200.fc4

Please let me know if there is anything I can test or check

Comment 4 POE 2025-10-07 06:46:17 UTC
This issue has now been resolved for me 

I'm currently running Linux 6.16.10-200.fc42.x86_64

Comment 5 Ambrogio 2025-10-09 09:18:16 UTC
I can confirm issue is resolved with new kernel release 6.16.10-200.fc42.x86_64

Regards
 Ambrogio


Note You need to log in before you can comment on or make changes to this bug.