Bug 1808784

Summary: Boot fails after update to kernel-5.5.6-201.fc31.x86_64
Product: [Fedora] Fedora Reporter: itblaked
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 31CC: airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, redhat-bugs, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-5.5.7-200.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-02 19:05:14 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
kernel boot log 5.5.6-201
none
boot log from kernel-5.6.0-0.rc3.git2.1.fc33.x86_64 none

Description itblaked 2020-03-01 08:13:26 UTC
1. Please describe the problem:
Post upgrade, system fails to boot into new kernel

2. What is the Version-Release number of the kernel:
kernel-5.5.6-201.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 :


Yes, worked in prior kernel 5.5.5-201

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

Attempt to boot into kernel-5.5.6-201.fc31.x86_64


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

TBC
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.

Comment 1 itblaked 2020-03-01 08:32:38 UTC
Ok, correction to question 6, I had the wireguard module enabled on the kernel.

Attached kernel logs.

Comment 2 itblaked 2020-03-01 08:33:25 UTC
Created attachment 1666717 [details]
kernel boot log 5.5.6-201

Comment 3 itblaked 2020-03-01 09:13:44 UTC
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``:

No - tested with kernel-5.6.0-0.rc3.git2.1.fc33.x86_64.txt

Attaching logs for boot from said kernel

Comment 4 itblaked 2020-03-01 09:14:26 UTC
Created attachment 1666730 [details]
boot log from kernel-5.6.0-0.rc3.git2.1.fc33.x86_64

Comment 5 Hans de Goede 2020-03-01 13:04:22 UTC
This is a known issue on devices which use the new sof-hda audio driver because they have digital mics. This has been fixed in 5.5.7, which is in updates-testing now.

The following should work to update your kernel to 5.5.7:

sudo dnf --enablerepo=updates-testing update 'kernel*'

Comment 6 Hans de Goede 2020-03-01 13:11:31 UTC
*** Bug 1808827 has been marked as a duplicate of this bug. ***

Comment 7 itblaked 2020-03-01 19:47:08 UTC
(In reply to Hans de Goede from comment #5)
> This is a known issue on devices which use the new sof-hda audio driver
> because they have digital mics. This has been fixed in 5.5.7, which is in
> updates-testing now.
> 
> The following should work to update your kernel to 5.5.7:
> 
> sudo dnf --enablerepo=updates-testing update 'kernel*'

Thanks

Comment 8 itblaked 2020-03-01 20:15:24 UTC
I installed kernel 5.5.7 with alsa-firmware from latest-testing repo and microphone/speaker both working successfully.

Comment 9 Fedora Update System 2020-03-02 19:05:14 UTC
kernel-5.5.7-200.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.