Bug 1755107

Summary: 5.3.0-1.fc31.x86_64: Kernel panic on reboot
Product: [Fedora] Fedora Reporter: Ankur Sinha (FranciscoD) <sanjay.ankur>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: airlied, bskeggs, bugzilla, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, steved, taaem
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-03 17:07:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Picture of kernel panic on reboot.
none
Picture of kernel panic from a second boot none

Description Ankur Sinha (FranciscoD) 2019-09-24 19:12:49 UTC 
Created attachment 1618703 [details]
Picture of kernel panic on reboot.

1. Please describe the problem:

On rebooting the system, the kernel panics and hangs. It does not happen if I power off and boot.


2. What is the Version-Release number of the kernel:
5.3.0-1.fc31.x86_64

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 :

I only started to notice this after upgrading to F31 last week. I did not notice see this in F30 at all. I still have the F30 kernel installed: kernel-core-5.2.14-200.fc30.x86_64

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

- reboot system


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

I've not tried this yet. I'll try it next.


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.

Unfortunately, the boot does not seem to be logged at all in the journal. Images from two such panics are attached.
Comment 1 Ankur Sinha (FranciscoD) 2019-09-24 19:13:24 UTC 
Created attachment 1618704 [details]
Picture of kernel panic from a second boot
Comment 2 Ankur Sinha (FranciscoD) 2019-09-24 19:14:00 UTC 
My system is a Thinkpad E490: https://linux-hardware.org/?probe=e5c277ee79
Comment 3 Chris Murphy 2019-09-26 20:52:54 UTC 
I suggest removing 'quiet rhgb' and reproduce the crash while taking video with a cell phone because it looks like the actual problem is in a call trace above what's shown.
Comment 4 taaem 2019-09-29 14:29:20 UTC 
I've seen that issue too on my Thinkpad, I could temporarily fix it by disabling the options that enable the new vendor plymouth screen (https://hansdegoede.livejournal.com/20632.html).
I enabled the options again just now and so far I could boot.
Comment 5 Ankur Sinha (FranciscoD) 2019-10-02 09:04:58 UTC 
Ah, if that's the case, it's a bug worth reporting to Hans. I'll try that to confirm too.

Could you please list the steps you used so that all the info is collected here on the bug?
Comment 6 Ankur Sinha (FranciscoD) 2019-10-02 09:10:04 UTC 
sudo plymouth-set-default-theme -R spinner 

did not solve the issue here. Is this what you had done?
Comment 7 taaem 2019-10-02 09:13:49 UTC 
No, I did switch my BIOS settings from UEFI only and CSM off to UEFI first and CSM on, and then I could boot just fine.
But I switched it back on the 29th and so far I had no issue, so I don't really know if it related or maybe already fixed by a kernel update.
Comment 8 Ankur Sinha (FranciscoD) 2019-10-02 10:07:59 UTC 
Ah, well, I removed `rhgb quiet` and it went away, and now I've added `rhgb quiet` back but it still boots fine. Not a clue what happened here. I'll leave this open for a bit in case I notice it again.
Comment 9 Justin M. Forbes 2020-03-03 16:23:15 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs.

Fedora 31 has now been rebased to 5.5.7-200.fc31.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32.

If you experience different issues, please open a new bug report for those.