Bug 2266057

Summary: Irregular behavior after suspend (auto-wake + I/O device blackout)
Product: [Fedora] Fedora Reporter: sub
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED COMPLETED QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 39CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarod, josef, kernel-maint, linville, masami256, mchehab, nixuser, ptalbert, py0xc3, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-03-04 10:36:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
the dmesg.txt of my last boot into Fedora none

Description sub 2024-02-26 14:09:02 UTC 
Created attachment 2018945 [details]
the dmesg.txt of my last boot into Fedora

1. Please describe the problem:

After updating to kernel version 6.7.5, the suspend function no longer works as intended; suspending the computer once will wake itself up after 5'' and doing it twice kills all I/O (USB devices, monitor etc) while the computer is still seemingly on. You have to manually shut the computer down and reboot in order to regain access to the computer.

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

6.7.5 (and 6.7.6)

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 :

It did work properly on F39 with kernel version 6.7.4 (I rolled back to 6.7.4 and suspend works as intended)

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

It happens after clicking on Suspend from the top right menu in GNOME.

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``:

It still occurs on the latest Rawhide kernel. (6.8.0)

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

No.

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.

Attaching below.
Comment 1 Christopher Klooz 2024-02-27 11:24:28 UTC 
There is an ask.fedora ticket of the user about this: https://discussion.fedoraproject.org/t/cannot-suspend-computer-amd-dgpu-does-not-work-after-kernel-update-6-7-5/106362  
  
The user seems to have installed 6.7.5 using the normal dnf updates, and additionally tested 6.7.6 through the bodhi update [1] that is still in testing. They report that 6.7.4 always works properly, while 6.7.5 and 6.7.6 always have the reported problems.  
  
The user experiences two problems on 6.7.5 & 6.7.6 for which they wrote two bug reports: the other is BZ#2266062

[1] https://bodhi.fedoraproject.org/updates/FEDORA-2024-d16d94b00d
Comment 2 sub 2024-03-04 10:34:28 UTC 
Reporting back after updating to kernel 6.7.7.

This update fixes the suspend bug, as well as the missing AMD dGPU bug I reported right after this one:

https://bugzilla.redhat.com/show_bug.cgi?id=2266062

Thank you for your hard work.