https://bugzilla.suse.com/show_bug.cgi?id=1180344 Bug ID: 1180344 Summary: Kernel 5.10.1 fails to boot with workqueue lockup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: adam@valkor.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 844693 --> https://bugzilla.suse.com/attachment.cgi?id=844693&action=edit journal from failed boot Linux 5.10.1 on my Thinkpad X1 Carbon Gen 7 fails to boot with workqueue lockup messages and a failure to mount /home. I've given it 10 minutes, but it will not complete booting. Previous kernels, including the fallback 5.9.14 do not exhibit this behavior. Dec 24 18:00:05 think kernel: BUG: workqueue lockup - pool cpus=5 node=0 flags=0x0 nice=0 stuck for 50s! Dec 24 18:00:05 think kernel: Showing busy workqueues and worker pools: Dec 24 18:00:05 think kernel: workqueue events: flags=0x0 Dec 24 18:00:05 think kernel: pwq 10: cpus=5 node=0 flags=0x0 nice=0 active=11/256 refcnt=12 Dec 24 18:00:05 think kernel: in-flight: 840:request_firmware_work_func Dec 24 18:00:05 think kernel: pending: delayed_fput, drm_fb_helper_dirty_work [drm_kms_helper], free_work, kfree_rcu_monitor, kernfs_notify_workfn, rfkill_global_led_trigger_worker [rfkill], smp_call_on_c> Dec 24 18:00:05 think kernel: pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 Dec 24 18:00:05 Previous kernels, including the fallback 5.9.14 do not exhibit this behavior. think kernel: pending: vmstat_shepherd Dec 24 18:00:05 think kernel: workqueue events_long: flags=0x0 Dec 24 18:00:05 think kernel: pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 Dec 24 18:00:05 think kernel: in-flight: 143:ucsi_init_work [typec_ucsi] Dec 24 18:00:05 think kernel: workqueue events_unbound: flags=0x2 Dec 24 18:00:05 think kernel: pwq 16: cpus=0-7 flags=0x4 nice=0 active=4/512 refcnt=6 Dec 24 18:00:05 think kernel: in-flight: 58:fsnotify_connector_destroy_workfn fsnotify_connector_destroy_workfn, 63:fsnotify_mark_destroy_workfn fsnotify_mark_destroy_workfn Dec 24 18:00:05 think kernel: workqueue rcu_gp: flags=0x8 Dec 24 18:00:05 think kernel: pwq 10: cpus=5 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 Dec 24 18:00:05 think kernel: pending: process_srcu Dec 24 18:00:05 think kernel: workqueue mm_percpu_wq: flags=0x8 Dec 24 18:00:05 think kernel: pwq 10: cpus=5 node=0 flags=0x0 nice=0 active=2/256 refcnt=4 Dec 24 18:00:05 think kernel: pending: vmstat_update, lru_add_drain_per_cpu BAR(907) Dec 24 18:00:05 think kernel: workqueue kec_query: flags=0x0 Dec 24 18:00:05 think kernel: pwq 10: cpus=5 node=0 flags=0x0 nice=0 active=1/16 refcnt=2 Dec 24 18:00:05 think kernel: pending: acpi_ec_event_processor Dec 24 18:00:05 think kernel: workqueue usb_hub_wq: flags=0x4 Dec 24 18:00:05 think kernel: pwq 10: cpus=5 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 Dec 24 18:00:05 think kernel: pending: hub_event [usbcore] Dec 24 18:00:05 think kernel: pool 0: cpus=0 node=0 flags=0x0 nice=0 hung=0s workers=4 idle: 5 770 7 Dec 24 18:00:05 think kernel: pool 10: cpus=5 node=0 flags=0x0 nice=0 hung=50s workers=4 idle: 764 43 133 Dec 24 18:00:05 think kernel: pool 16: cpus=0-7 flags=0x4 nice=0 hung=0s workers=8 idle: 8 60 59 62 61 64 ��� rpm -qa | grep kernel-default kernel-default-5.10.1-1.1.x86_64 kernel-default-5.9.14-1.2.x86_64 -- You are receiving this mail because: You are the assignee for the bug.