Bug 1174391 - /lib/firmware update causes Dell 7300 to hang on boot after loading initrd ramdisk
/lib/firmware update causes Dell 7300 to hang on boot after loading initrd ra...
Status: RESOLVED INVALID
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel
Current
x86-64 openSUSE Factory
: P5 - None : Critical (vote)
: ---
Assigned To: openSUSE Kernel Bugs
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-07-22 13:32 UTC by Jan Meyer
Modified: 2020-08-03 12:52 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Meyer 2020-07-22 13:32:13 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
Build Identifier: 

Hi,
last Saturday 16.07. I did "zypper dup" on my Tumbleweed Dell Latitude 7300 laptop and rebooted. The laptop froze directly after the messages "Loading kernel 5.7.7, Loading Ramdisk".

Booting from the earlier kernel version 5.7.5 worked once in recovery mode but on a second attempt (and running mkinitrd) not either anymore. Booting from any older read-only snapshot did not help either (could my snapshotting set-up be broken/incomplete here??). I was pretty desperate.

Then I realized that it could be something with UEFI secure boot and disabled secure boot. Then I chrooted into my broken Tumbleweed installation with a life cd. Next restored /lib/firmware directly directly from an older snapshot (the older fire versions were there). Rebooted. Works again - without secureboot with older firmware.

So for now I can work again. But I want to inform to spare others from this desperation ... and eventually to get a fix to the firmware packages.

Best regards,

Jan



Reproducible: Always

Steps to Reproduce:
1.update to latest firmware packages 
2.reboot
Actual Results:  
Grub2 bootloader starts normally
Computer freezes after message "Loading Ramdisk"



Newly installed and not working firmware versions:

kernel-firmware-intel-20200702-1.1.noarch
kernel-firmware-nvidia-20200702-1.1.noarch
kernel-firmware-realtek-20200702-1.1.noarch
... all further firmwares have same rpm version 

for standard tumbleweed kernel 5.7.7-1-default 64bit

Some general information on my Dell Latitude 7300 Laptop

Intel Coffee Lake is the Chipset, I believe

>>:~ # lspci 
00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30)
00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30)
00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30)
00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30)
00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30)
00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30)
00:15.3 Serial bus controller [0c80]: Intel Corporation Device 9deb (rev 30)
00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30)
00:19.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Host Controller (rev 30)
00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device 9db3 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30)
00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30)
00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30)
01:00.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
02:00.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
02:01.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
02:02.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
03:00.0 System peripheral: Intel Corporation JHL6340 Thunderbolt 3 NHI (C step) [Alpine Ridge 2C 2016] (rev 02)
04:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
05:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
05:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
06:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge DD 2018] (rev 06)
39:00.0 USB controller: Intel Corporation JHL6340 Thunderbolt 3 USB 3.1 Controller (C step) [Alpine Ridge 2C 2016] (rev 02)
3a:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
3b:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983

>>:~ # lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 005: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 006 Device 004: ID 05e3:0612 Genesys Logic, Inc. Hub
Bus 006 Device 003: ID 0bda:0413 Realtek Semiconductor Corp. 
Bus 006 Device 002: ID 0bda:0487 Realtek Semiconductor Corp. Dell dock
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 004: ID 413c:b06e Dell Computer Corp. 
Bus 005 Device 011: ID 413c:b06f Dell Computer Corp. 
Bus 005 Device 010: ID 0bda:402e Realtek Semiconductor Corp. 
Bus 005 Device 008: ID 0b0e:0300 GN Netcom Dell dock
Bus 005 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 005 Device 003: ID 0bda:5413 Realtek Semiconductor Corp. 
Bus 005 Device 002: ID 0bda:5487 Realtek Semiconductor Corp. Dell dock
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 413c:81d7 Dell Computer Corp. DW5821e Snapdragon X20 LTE
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0a5c:5843 Broadcom Corp. 58200
Bus 001 Device 002: ID 1bcf:28c4 Sunplus Innovation Technology Inc. Integrated_Webcam_HD
Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Comment 1 Takashi Iwai 2020-07-22 15:45:21 UTC
It's a known problem regarding the AMDGPU firmware update that broke with this kernel-firmware update, but your case doesn't seem that.  Or is it with AMDGPU?

Other than that, the only other changes in this update were Realtek rtl8125b stuff, but this doesn't look matching with yours (with Realtek but different chips).

Could you try to identify which kernel-firmware-xxx package may break things?
It'd be greatly appreciated if we can know that.

You can save initrd file beforehand (just copy /boot/initrd-xxx to /boot/initrd-xxx.old), and choose it in GRUB menu for recovery, too.
Comment 2 Jan Meyer 2020-07-26 18:32:30 UTC
In the meantime I tested further:

First, I rebooted and booted with the "new" initrd that was based on mkinitrd with the latest firmware set (the complete set). I did that by rebooting and then pressing 'e' in grub2 menu and changed the initrd to the initrd....new, which I had prepared before.

Then I actually fully turned off my laptop and turned it on again. I am using a nvme ssd with hardware encryption, which is activated pre-boot with sedutil (https://sedutil.com/). Hence sedutil boots first, I enter my passphrase, then the laptop warm-reboots again and grub2 is started from the nvme SSD.

Then I tried some ~10 times to boot with different initrd's (old and new) and older 5.7.5 kernel - all unsuccessfully freezing after "loading kernel image, loading ramdisk". In the meantime I successfully booted an older tumbleweed life image.

Finally I tried again after a short break, this time with power adaptor (not the thunderbird docking station) plugged in and I could again boot with the old initrd.

It seems(!) that my problem may be after all not firmware related. But related to something else in the boot process. But what can it be? I get zero error messages.

Is there anything else I can do to narrow down my problem?
Could this sedutil pre-boot process be part of the problem, if the laptop afterwards properly reboots? I.e. can that be excluded?

P.S. I noticed that there is a minor update of the BIOS firmware available. I am currently running 1.7.4 and will try next upgrading to 1.9.1
Comment 3 Jan Meyer 2020-07-26 19:05:09 UTC
upgrade to system BIOS v1.9.1 worked. And booting with new firmware also worked again.

Could it really be related to me booting now with AC powersupply??

Below some information on that BIOS update.


-----
Dell firmware
  Upgrade available for System Firmware from 1.7.4 (22.05.2020) to 1.9.1 (30.06.2020)
  - Updated the Power Delivery firmware.
  - Updated the Intel Rapid Storage Technology firmware.
  https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=03fmp&oscode=wt64a&productcode=latitude-13-7300-laptop&lwp=rt
Comment 4 Takashi Iwai 2020-08-03 12:52:18 UTC
Honestly speaking, I don't know :)
What I can say is that there was no kernel changes relevant with your hardware components, so I won't be surprised if the AC power supply was really a cause.

In anyway, let's close the bug.  Feel free to reopen if the same problem persists.  Thanks.