Bug 206743 - kernel panic at the end of shutdown
Summary: kernel panic at the end of shutdown
Status: RESOLVED CODE_FIX
Alias: None
Product: Other
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: other_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-03 07:32 UTC by matthias
Modified: 2020-03-08 07:27 UTC (History)
1 user (show)

See Also:
Kernel Version: any 5.x
Subsystem:
Regression: No
Bisected commit-id:


Attachments
video showing console during shutdown (1.03 MB, video/mp4)
2020-03-03 07:32 UTC, matthias
Details

Description matthias 2020-03-03 07:32:47 UTC
Created attachment 287775 [details]
video showing console during shutdown

Any kernel 5.x in combination with system 243 or 244 crashes at the end of the shutdown process. 


No crash with systemd 242 and kernel 5.x. No crash with kernel 4.19 and systemd 243/244.

Although the crash seems to be triggered by systemd it is actually the kernel which is crashing.

The crash seems to happen only for Ryzen 7 CPUs. At least this is what is suggested here: https://github.com/systemd/systemd/issues/14829#issuecomment-583819893


There are no log messages because the crash happens when the journal has been stopped already.  I can only provide a video which shows the relevant messages on the console.
Comment 1 Torsten Hilbrich 2020-03-07 20:35:37 UTC
This is not limited to Ryzen CPUs, I have seen this issue with Intel Core i5-7200 CPUs.

I can confirm that kernel 4.19 works without any problems and 5.4.19 has this problem. In my case systemd was version 243.
Comment 2 matthias 2020-03-08 07:27:13 UTC
The issue has been solved for me with the recent kernel updates.
With kernel 5.4.24 or 5.5.8 I do not see the crash anymore. I verified by downgrading to kernel 5.4.23 and 5.5.7 which brings back the kernel panic during shutdown. This is with systemd 244.3

Both kernel 5.4.24 and 5.5.8 come with a whole bunch of fixes related to NVME drives. My kernel panic screenshots show nvme+irq messages. I assume the new NVME code fixes my issue.

I am closing the issue.

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