Bug 2013053 - Kernel panic on reboot after install
Summary: Kernel panic on reboot after install
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 35
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2021-10-12 00:43 UTC by russ.butler
Modified: 2022-12-13 15:40 UTC (History)
26 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:40:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description russ.butler 2021-10-12 00:43:33 UTC
Description of problem:
Kernel panics on reboot after install due to timeout when using a slow virtual USB CD drive.

Version-Release number of selected component (if applicable):
Fedora Linux 35 (Server Edition Prerelease)

How reproducible:
Occurred 2 for 2 times when installing Fedora


Steps to Reproduce:
1. Install Fedora 35 on an Ampere Altra remotely using its BMC's web interface to attach a virtual USB cd.
2. Click reboot button after the install finishes

Actual results:

A timeout occurs during shutdown, followed by a kernel panic as shown below

[  OK  ] Unmounted /run/credentials/systemd-sysusers.service.
[FAILED] Failed unmounting /run/install/repo.
[  OK  ] Unmounted /run/rootfsbase.
...
[  OK  ] Reached target System Reboot.
[ 1659.472200] watchdog: watchdog0: watchdog did not stop!
/usr/bin/sh: error while loading [ 1659.478948] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
shared libraries: libtinfo.so.6:[ 1659.489429] CPU: 49 PID: 1 Comm: shutdown Not tainted 5.14.9-300.fc35.aarch64 #1
 cannot open shared object file:[ 1659.499585] Hardware name: WIWYNN Mt.Jade Server System B81.03001.0005/Mt.Jade Motherboard, BIOS 0.9.20200724 2020/07/24
 No such file or directory
[ 1659.513220] Call trace:
[ 1659.518083]  dump_backtrace+0x0/0x1c0
[ 1659.521749]  show_stack+0x24/0x30
[ 1659.525053]  dump_stack_lvl+0x68/0x84
[ 1659.528715]  dump_stack+0x18/0x34
[ 1659.532018]  panic+0x144/0x350
[ 1659.535067]  do_exit+0x458/0x460
[ 1659.538289]  do_group_exit+0x44/0xac
[ 1659.541854]  __wake_up_parent+0x0/0x3c
[ 1659.545591]  invoke_syscall+0x50/0x120
[ 1659.549334]  el0_svc_common+0x48/0x100
[ 1659.553072]  do_el0_svc+0x34/0xa0
[ 1659.556376]  el0_svc+0x2c/0x54
[ 1659.559422]  el0t_64_sync_handler+0xa4/0x130
[ 1659.563681]  el0t_64_sync+0x19c/0x1a0
[ 1659.567417] SMP: stopping secondary CPUs
[ 1659.572464] Kernel Offset: 0x49472eae0000 from 0xffff800010000000
[ 1659.578544] PHYS_OFFSET: 0x80000000
[ 1659.582020] CPU features: 0x000042c1,a3302e42
[ 1659.586366] Memory Limit: none
[ 1659.589454] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 ]---

Expected results:

Successful shutdown

Comment 1 Ben Cotton 2022-11-29 17:08:53 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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 '35'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Ben Cotton 2022-12-13 15:40:10 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

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