Bugzilla – Bug 1222914
Upgrade from kernel 5.14.21-150500.55.39-default to kernel 5.14.21-150500.55.44-default broke on my laptop
Last modified: 2024-05-21 06:34:57 UTC
When I tried to install the upgrade mentioned in the summary it breaks and hangs during the bootup process for the new system and badly hangs requiring me to power cycle my laptop. I have frozen and locked my laptop at vmlinuz-5.14.21-150500.55.39-default for now, but that means I can no longer install any kernel patches or upgrades. I am not sure of the cause of the hang up but have narrowed it down to probably ??? either an inability to properly query my network interfaces (it sometimes stalls out when trying to get an IP address from my DHCP server) for their identity and capabilities) or perhaps something is wrong with the nVidia drivers. I have a relatively new Dell laptop as described here - # inxi -CGMSnaz System: Kernel: 5.14.21-150500.55.39-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.39-default root=UUID=ce027c75-c647-4b4b-8c6a-e5fb48f41513 splash=silent preempt=full mitigations=auto quiet security=apparmor Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM Distro: openSUSE Leap 15.5 Machine: Type: Laptop System: Dell product: XPS 15 9530 v: N/A serial: <filter> Chassis: type: 10 serial: <filter> Mobo: Dell model: 0GY0F9 v: A00 serial: <filter> UEFI: Dell v: 1.7.0 date: 08/14/2023 CPU: Info: model: 13th Gen Intel Core i9-13900H socket: U3E1 bits: 64 type: MST AMCP arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+ process: Intel 7 (10nm) family: 6 model-id: 0xBA (186) stepping: 2 microcode: 0x411C Topology: cpus: 1x cores: 14 mt: 6 tpc: 2 st: 8 threads: 20 smt: enabled cache: L1: 1.2 MiB desc: d-8x32 KiB, 6x48 KiB; i-6x32 KiB, 8x64 KiB L2: 11.5 MiB desc: 6x1.2 MiB, 2x2 MiB L3: 24 MiB desc: 1x24 MiB Speed (MHz): avg: 540 high: 682 min/max: 400/5200:5400:4100 base/boost: 4851/5400 scaling: driver: intel_pstate governor: powersave volts: 1.3 V ext-clock: 100 MHz cores: 1: 440 2: 473 3: 404 4: 587 5: 544 6: 680 7: 468 8: 682 9: 564 10: 662 11: 443 12: 583 13: 624 14: 459 15: 532 16: 489 17: 488 18: 553 19: 580 20: 546 bogomips: 119807 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: mmio_stale_data status: Not affected Type: retbleed status: Not affected Type: spec_rstack_overflow status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: Dell driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: 0000:00:02.0 chip-ID: 8086:a7a0 class-ID: 0300 Device-2: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile] vendor: Dell driver: N/A alternate: nouveau, nvidia_drm, nvidia non-free: N/A status: unknown device ID bus-ID: 0000:01:00.0 chip-ID: 10de:28a0 class-ID: 0302 Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 3-6:3 chip-ID: 0c45:6a22 class-ID: fe01 serial: <filter> Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.5 compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: iris gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 507x285mm (19.96x11.22") s-diag: 582mm (22.9") Monitor-1: eDP-1 model: Samsung 0x414d built: 2020 res: 1920x1080 hz: 60 dpi: 145 gamma: 1.2 size: 336x210mm (13.23x8.27") diag: 396mm (15.6") ratio: 16:10 modes: 3456x2160 API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel Graphics (RPL-P) direct render: Yes Network: Device-1: Intel Raptor Lake PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 0000:00:14.3 chip-ID: 8086:51f1 class-ID: 0280 IF: wlan0 state: up mac: <filter> Device-2: ASIX AX88179 Gigabit Ethernet type: USB driver: ax88179_178a bus-ID: 2-1.3.2:4 chip-ID: 0b95:1790 class-ID: ff00 serial: <filter> IF: eth0 state: down mac: <filter> Please refer to the thread on users@lists.opensuse.org titled "Yikes! Looks like an update has screwed up my laptop" to see a discussion I had with the user community about this issue, for some additional information. They advised me to submit this bug report. I will be happy to provide any additional information requested, and I will see if I can capture a boot log file and add it in a followup comment.
Created attachment 874317 [details] boot.msg
I have attached the boot.msg file created when I tried to boot up OpenSuSE 15.5 with kernel 5.14.21-150500.55.44-default. Unfortunately Buzilla is encountering an internal server error when I try to attach a second file - boot.log I will keep fiddling with it to see if I can find a way to attach it. On this attempt, I let the boot process run for a half hour and it finally reached the desktop! But anything that had to use or work with networks failed. After a few minutes the KDE/Plasma desktop itself froze up and I had to power cycle my laptop at that point. I saw a number of weird messages also about start jobs running. These messages have a timestamp appended to them, one part indicates how long the start job has been running and the other part seems to indicate a limit placed on the start job. But when the limit is reached, the limit seems to be set to a higher value, letting the start job continue to run. One of these kept this up for 15 minutes, which seems to be ridiculous! Others indicate there is no limit, which seems to be incredibly dangerous! As I said this seems weird but I dunno if it is the proper behavior or not.
Do kernels 55.49 & 55.52 impose the same issue as 55.44? Comment #0 mailing list thread was in January, here: https://lists.opensuse.org/archives/list/users@lists.opensuse.org/thread/AFD6CZWORAWO7FFPZ33BNSFMLJ4LKEXL/
Created attachment 874321 [details] boot.log part 1
Created attachment 874322 [details] boot.log part 2
Could this be Optimus or RTX 4060 driver trouble?
(In reply to Felix Miata from comment #6) > Could this be Optimus or RTX 4060 driver trouble? I don't know. I don't see neither nouveau nor nvidia driver being mentioned in the the boot log. Maybe things are freezing before.
(In reply to Felix Miata from comment #3) > Do kernels 55.49 & 55.52 impose the same issue as 55.44? > > Comment #0 mailing list thread was in January, here: > https://lists.opensuse.org/archives/list/users@lists.opensuse.org/thread/ > AFD6CZWORAWO7FFPZ33BNSFMLJ4LKEXL/ Hello again Felix, uh I am going to need some hand holding here to be able to answer your question. I don't know how to set up grub to allow me to install and optionally test/run kernels 55.49 and 55.52. Right now I can try and boot up 55.44 (which fails) and I can manually select 55.39 which still does work. I have things frozen, as described in the mail list, so that 55.39 does not get deleted. So I will need help and a description of the commands I need to execute in order to install kernels 55.49 and 55.52 so that I can optionally select and boot them up as well. (while keeping 55.39 around for the time being) Sorry to be naive about kernels and grub, I will do some Duck Duck Go'ing to see what I can grok on my own, but I am a stranger in a strange land now!
Created attachment 874337 [details] Journalctl Felix Miata asked me to create and save the journalctl log after I booted up the OpenSuSE system with the kernel 5.14.21-150500.55.44-default. (The network is badly broken when this kernel is booted up.) This journal shows a lot of errors that may be useful. I have added it as another attachment to this bugzilla report.
First off, try the very latest kernel in OBS Kernel:SLE15-SP5 repo: http://download.opensuse.org/repositories/Kernel:/SLE15-SP5/pool/ But this is an unofficial build, hence you have to disable Secure Boot in BIOS beforehand. If it were about graphics, you can try to boot with nomodeset boot option to disable the native graphics, and you can see whether it still crashes or not. Please check it.