Bug 2241854 - Unable to gracefully reboot or shut down after kernel-6.5.5-200.fc38.x86_64 update
Summary: Unable to gracefully reboot or shut down after kernel-6.5.5-200.fc38.x86_64 u...
Keywords:
Status: CLOSED DUPLICATE of bug 2241279
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 38
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-10-03 04:11 UTC by scchicago
Modified: 2023-10-03 11:55 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-10-03 11:55:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
journalctl dmesg log requested by guided form (99.97 KB, text/plain)
2023-10-03 04:14 UTC, scchicago
no flags Details

Description scchicago 2023-10-03 04:11:40 UTC
1. Please describe the problem:
On Dell Optiplex 7040 hardware using the latest kernel (kernel-6.5.5-200.fc38.x86_64 ) my system is unable to power off or reboot gracefully. A hard power down is required to recover.

2. What is the Version-Release number of the kernel:
6.5.5-200.fc38.x86_64

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 :
Yes.The previously installed kernel version, kernel-6.4.15-200.fc38.x86_64, works as expected.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Yes, it occurs when booted with kernel-6.5.5-200.fc38.x86_64 selected in Grub

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``:
The latest available rawhide kernel is still affected.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
nvidia driver from RPMfusion. I did remove via DNF yielding no results.

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.

There is nowhere to attach a file on this form.

Reproducible: Always

Comment 1 scchicago 2023-10-03 04:14:12 UTC
Created attachment 1991697 [details]
journalctl dmesg log requested by guided form

Issue occurs not at boot, but during shut down or reboot. Attached log is from a failed reboot attempt.

Comment 2 Justin M. Forbes 2023-10-03 11:55:21 UTC

*** This bug has been marked as a duplicate of bug 2241279 ***


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