Kernel 5.10.1 problems?

After updating Tumbleweed today, which included the new kernel 5.10.1-1, Tumbleweed would boot, but hang. I’ve booted into kernel 5.9.14 to be able to write this. What do I need to do to be able to use the new kernel? I’ve never seen this happen before.

Hi and welcome to the Forum :slight_smile:
When you say hang, during the boot process, getting to your login GUI or desktop?

What sort of hardware and graphics are involved?

Look for more info by pressing the esc key during boot, or temporarily disable plymouth at boot by editing (press the e key) grub and adding plymouth.enabled=0

It starts normally. I see the Lenovo logo and under that, the Tumbleweed logo. The little circle thing rotates and that’s about it.

As for the hardware, it’s a Lenovo IdeaPad L340 with a quad-core CPU (Intel(R) Corporation.Intel(R)Core45U CPU @ 2.10GH) and UHD Graphics 620 (Whiskey Lake). There have been kernel updates before, and everything went smoothly. Not sure what happened this time, although I see more updates waiting as I type this.

I’ll give your suggestions a try to see what happens.

That’s “plymouth.enable=0”.

So, I was sitting here swearing at the machine, and tried going to the advanced setting thing in the grub menu and booting kernel 5.10 from the first entry (theoretically the same one as the main boot menu). Be darned if the thing didn’t boot and run properly. Running “uname -a” shows me this:

Linux orenda 5.10.1-1-default #1 SMP Sun Dec 20 07:24:34 UTC 2020 (d14c73f) x86_64 x86_64 x86_64 GNU/Linux

So, I’ll print the 2 entries to see what the difference is, and make mods(?) as appropriate.

The advanced menu entry worked once. Back to the drawing board. BTW, the plymouth thing didn’t work,

Same error for me with kernel 5.10.1 - using plasma. It starts to load then lines and lines of error messages. I have a normal Dell p/c with standard hardware. Tried a fresh install and the sme errors. Only way to stop the p/c is by holding the start button until it switches off. Might be hardware issue as I tried a fresh install on a spare p/c and that worked OK.

I was going to try a fresh install on another drive. I found another distro on it. I ran it, did updates, and it runs well with kernel 5.10.2. Same laptop, different drive.

My AMD Ryzen system TW/KDE wont boot with this kernel either. I’ll look imto it later to see what is happening.

Stuart

Looking at the journal for the boot with tis kernel the only thing I can find which is different to the old kernel is as follows:-


Dec 25 11:10:58 Tumbleweed.Crowhill kernel: BUG: workqueue lockup - pool cpus=6 node=0 flags=0x0 nice=0 stuck for 57s!
Dec 25 11:10:58 Tumbleweed.Crowhill kernel: Showing busy workqueues and worker pools:
Dec 25 11:10:58 Tumbleweed.Crowhill kernel: workqueue events: flags=0x0
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:   pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=11/256 refcnt=12
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:     in-flight: 1089:request_firmware_work_func
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:     pending: delayed_fput, kfree_rcu_work, free_work, kfree_rcu_monitor, kernfs_notify_workfn, release_one_tty, release_one_tty, release_one_tty, do_free_init, deferred_probe_work_func
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:   pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=2/256 refcnt=3
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:     pending: vmstat_shepherd, drm_fb_helper_dirty_work [drm_kms_helper]
Dec 25 11:10:58 Tumbleweed.Crowhill kernel: workqueue events_unbound: flags=0x2
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:   pwq 64: cpus=0-31 flags=0x4 nice=0 active=4/512 refcnt=7
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:     in-flight: 167:fsnotify_connector_destroy_workfn fsnotify_connector_destroy_workfn, 64:fsnotify_mark_destroy_workfn fsnotify_mark_destroy_workfn BAR(1020)
Dec 25 11:10:58 Tumbleweed.Crowhill kernel: workqueue events_freezable: flags=0x4
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:   pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:     pending: pci_pme_list_scan
Dec 25 11:10:58 Tumbleweed.Crowhill kernel: workqueue events_power_efficient: flags=0x80
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:   pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:     pending: ioc_release_fn
Dec 25 11:10:58 Tumbleweed.Crowhill kernel: workqueue events_freezable_power_: flags=0x84
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:   pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:     pending: disk_events_workfn
Dec 25 11:10:58 Tumbleweed.Crowhill kernel: workqueue rcu_gp: flags=0x8
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:   pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:     pending: process_srcu
Dec 25 11:10:58 Tumbleweed.Crowhill kernel: workqueue mm_percpu_wq: flags=0x8
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:   pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=2/256 refcnt=4
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:     pending: vmstat_update, lru_add_drain_per_cpu BAR(6299)
Dec 25 11:10:58 Tumbleweed.Crowhill kernel: workqueue cgroup_destroy: flags=0x0
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:   pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=1/1 refcnt=5
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:     pending: css_release_work_fn
Dec 25 11:10:58 Tumbleweed.Crowhill kernel:     delayed: css_release_work_fn, css_release_work_fn, css_release_work_fn
Dec 25 11:10:58 Tumbleweed.Crowhill kernel: pool 12: cpus=6 node=0 flags=0x0 nice=0 hung=57s workers=4 idle: 49 892 190
Dec 25 11:10:58 Tumbleweed.Crowhill kernel: pool 64: cpus=0-31 flags=0x4 nice=0 hung=0s workers=13 idle: 168 162 62 8 63 61 60 58 59 171 172

Stuart

Just found 2 bugs in bugzilla 1180344 and 1178911

I get the same error message.

1178911 bug seems to point to the AMDGPU and a reset. The other is not yet clear if it’s the same. I might try my laptop later which has an Intel GPU. My desktop (this one I’m posting from) boots fine from kernel 5.9.14.1. Does that imply the AMDGPU code will be downlevel or will it be the latest level from the update and loaded dynamically?

Stuart

My desktop has a nvidia graphic card.

It might be a hard drive issue. The desktop with the problem has a ssd drive and the old desktop which I tried (which worked fine with the kernel) has just an old fashioned drive.

Hi
Tested here, TW machine, nvidia (GT710/460.27.04) and all ok… desktop here is intel/nvidia all ok as well.

I woke up facing the same issue. After one reset the system booted the desktop but was unusable. Then reset again and had the same output described above. My processor is an AMD Ryzen 4700u with integrated graphics.

I just updated my system and can confirm the problem.

Operating System: openSUSE Tumbleweed 20201223
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
Kernel Version: 5.9.14-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-7820HK CPU @ 2.90GHz
Memory: 62.7 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 630 + NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev ff) switched off by bbswitch -> optimus system]

When i boot kernel 5.10.1-1-default the system dies half way through booting (even when i try to boot to runlevel 3). The only way to recover is to switch the machine off.

 8.446893] BUG: unable to handle page fault for address: ffffb04bc1e4227b

is the last line i see before the system dies away. I will have to switch to permanent logs to see if there are more error messages.

Kernel 5.9.14-1-default still works.

Regards

susejunky

I have the same problem, laptop with Ryzen7 and Geforce GTX graphics. Tried several boots, very variable results, no OS start, start to desktop but no WiFi, hang on boot : same bugs as reported earlier, etc. Also had to reboot into an earlier kernel version to be able to write this.

Cf. my comment at https://bugzilla.suse.com/show_bug.cgi?id=1180344#c11, maybe it also applies to you.

I confirm what was said by Malcolm, Nvidia Graphics and Cpu Amd everything works perfectly

My computer


[FONT=monospace] inxi -Fi 
**System:    Host:** Linux-Area51 **Kernel:** 5.10.1-1-default x86_64 **bits:** 64 **Desktop:** KDE Plasma 5.20.4  
           **Distro:** openSUSE Tumbleweed 20201223  
**Machine:   Type:** Desktop **Mobo:** ASUSTeK **model:** M5A78L-M/USB3 **v:** Rev X.0x **serial:** <superuser/root required>  
           **BIOS:** American Megatrends **v:** 2101 **date:** 12/02/2014  
**CPU:       Topology:** Quad Core **model:** AMD FX-4300 **bits:** 64 **type:** MCP **L2 cache:** 2048 KiB  
           **Speed:** 1406 MHz **min/max:** 1400/3800 MHz **Core speeds (MHz):** **1:** 1406 **2:** 1406 **3:** 1405 **4:** 1406  
**Graphics:  Device-1:** NVIDIA GF119 [GeForce GT 610] **driver:** nvidia **v:** 390.138  
           **Display:** x11 **server:** X.Org 1.20.10 **driver:** nvidia **unloaded:** fbdev,modesetting,nouveau,nv,vesa  
           **resolution:** 1920x1080~60Hz  
           **OpenGL:** **renderer:** GeForce GT 610/PCIe/SSE2 **v:** 4.6.0 NVIDIA 390.138  
**Audio:     Device-1:** Advanced Micro Devices [AMD/ATI] SBx00 Azalia **driver:** snd_hda_intel  
           **Device-2:** NVIDIA GF119 HDMI Audio **driver:** snd_hda_intel  
           **Device-3:** Microsoft LifeCam VX-800 **type:** USB **driver:** snd-usb-audio,uvcvideo  
           **Sound Server:** ALSA **v:** k5.10.1-1-default  
**Network:   Device-1:** Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet **driver:** r8169  
           **IF:** enp3s0 **state:** up **speed:** 100 Mbps **duplex:** full **mac:** 9c:5c:8e:7c:a3:a7  
           **IP v4:** 192.168.178.102/24 **type:** dynamic noprefixroute **scope:** global  
           **IP v6:** fe80::925:cb17:2026:2e1/64 **type:** noprefixroute **scope:** link  
           **WAN IP:** 146.241.192.212  
**Drives:    Local Storage:** **total:** 521.66 GiB **used:** 62.39 GiB (12.0%)  
           **ID-1:** /dev/sda **vendor:** Kingston **model:** SV300S37A60G **size:** 55.90 GiB  
           **ID-2:** /dev/sdb **vendor:** Seagate **model:** ST500DM002-1BD142 **size:** 465.76 GiB  
**Partition: ID-1:** / **size:** 43.06 GiB **used:** 16.70 GiB (38.8%) **fs:** ext4 **dev:** /dev/sda2  
           **ID-2:** /boot **size:** 978.8 MiB **used:** 127.3 MiB (13.0%) **fs:** ext4 **dev:** /dev/sda1  
           **ID-3:** /home **size:** 10.66 GiB **used:** 3.53 GiB (33.1%) **fs:** ext4 **dev:** /dev/sda3  
           **ID-4:** /tmp **size:** 9.55 GiB **used:** 36.2 MiB (0.4%) **fs:** ext4 **dev:** /dev/sdb2  
           **ID-5:** /var **size:** 9.55 GiB **used:** 2.82 GiB (29.6%) **fs:** ext4 **dev:** /dev/sdb1  
**Swap:      Alert:** No Swap data was found.  
**Sensors:   System Temperatures:** **cpu:** 35.0 C **mobo:** 29.0 C **gpu:** nvidia **temp:** 42 C  
           **Fan Speeds (RPM):** **cpu:** 1679 **case-1:** 1231 **gpu:** nvidia **fan:** 40%  
**Info:      Processes:** 199 **Uptime:** 3h 19m **Memory:** 7.74 GiB **used:** 4.43 GiB (57.2%) **Shell:** bash **inxi:** 3.1.00 
 
[/FONT]