Bug 2349003 - Immediate power off on hang on 6.13.x when booting
Summary: Immediate power off on hang on 6.13.x when booting
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 41
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-02-28 12:04 UTC by Tad
Modified: 2025-12-16 18:54 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-12-16 18:54:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tad 2025-02-28 12:04:19 UTC
1. Please describe the problem:

after showing the plymouth splash and some errors briefly it immediately powers off, almost like it was shorted out

the screen resolution is also very low when shown


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

6.13.3, 6.13.4, 6.13.5


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.12.x is stable


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

every time when booting


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

kernel-6.14.0-0.rc4.20250226gitac9c34d1e45a.38.fc43 doesn't power off but does hang and never boots


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.

hard to get since it powers off/hangs so early

8. extra information

This importantly only happens when booted with kernel command line argument `iommu.strict=1`.

I suspect this is amdgpu related.
This off/hanging behavior is happening when the second dedicated GPU in this laptop gets initialized. Ryzen 5800H with Radeon RX 6700M

I have another laptop without a dGPU that also has the hanging behavior on 6.13 and eventually goes completely black screen. Ryzen 7530U

I did check here, bz.kernel.org, and bodhi for similar reports but didn't find any.

Comment 1 Adam Williamson 2025-12-02 02:29:01 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Samyak Jain (RedHat) 2025-12-16 18:54:56 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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