Bug 1215544 - Kernel update to 5.14.21-150500.55.22-default - Kernel panic
Summary: Kernel update to 5.14.21-150500.55.22-default - Kernel panic
Status: RESOLVED WORKSFORME
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Leap 15.5
Hardware: x86-64 openSUSE Leap 15.5
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: openSUSE Kernel Bugs
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-20 20:40 UTC by Thomas Formella
Modified: 2023-10-25 03:04 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Formella 2023-09-20 20:40:47 UTC 
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.14.21-150500.55.22-default #1 SLE15-SP5 #####
Call Trace:
<TASK>
dump-stack_lvl+0x45/0x5b
panic +0x118/0x2f0
mount_block_root+0x317/0x347
? rdinit_setup 0x2f/0x2f
prepare_namespace+0x130/0x15f
kernel_init_freeable+0x26a/0x298
? rest_init+0xd0/0xd0
kernel_init+0x16/0x120
ret_from_fork+0x22/0x30
</TASK>
Kernel Offset: 0x4e00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---


CPU: Intel E5200
GPU: AMD RV710

Returning to 5.14.21-150500.55.19-default "solves" the problem.
Comment 1 Takashi Iwai 2023-10-24 13:49:10 UTC 
Could you check whether the problem persists with the latest update?
Comment 2 Thomas Formella 2023-10-25 02:57:45 UTC 
(In reply to Takashi Iwai from comment #1)
> Could you check whether the problem persists with the latest update?

Shortly afterwards, a hardware problem occured with my hdd. With a new hdd, the latest update went through without a problem. 

I guess that it's very likely, that in my case the updated kernel wasn't properly installed due to the faulty hdd and the kernel itself wasn't the the problem.

Sorry for bothering!
Comment 3 Thomas Formella 2023-10-25 03:04:26 UTC 
Kernel panic possibly caused by faulty hdd. Latest kernel works with new hdd.