Bug 2223088 - After an update, fedora 38 fails to boot past boot screen
Summary: After an update, fedora 38 fails to boot past boot screen
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-15 11:55 UTC by Graeme Murray
Modified: 2024-05-28 13:30 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-28 13:30:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
journalctl -b -1 (116.03 KB, text/plain)
2023-07-15 11:57 UTC, Graeme Murray
no flags Details

Description Graeme Murray 2023-07-15 11:55:56 UTC
following an update, the systems fails to boot past the boot screen. Pressing the esc key, produces nothing. Power off, then on again, systems boots as normal.

Reproducible: Always

Steps to Reproduce:
1.install an update
2. reboot, install happens as expected.
3. reboot and system hangs at boot screen.
4. reboot and system boots as normal
Actual Results:  
After an update system hangs on first full reboot.

Expected Results:  
to boot first time after an update.

Kernel: 6.3.12-200.fc38.x86_64
AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx (8) @ 2.300GHz

Comment 1 Graeme Murray 2023-07-15 11:57:19 UTC
Created attachment 1975914 [details]
journalctl -b -1

Comment 2 Aoife Moloney 2024-05-28 13:30:35 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 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.