滚动更新升级内核后无法开机

安装升级与设置
1

今天升级了一下，内核从 5.9 升级到了 5.10.1，无法开机。能显示开机动画，但一直卡住没有变化。能在 Grub 里用旧内核启动，也能使用 LiveCD。

内核日志 
[无关部分省略]
12 月 29 13:46:49 kernel: BUG: unable to handle page fault for address: ffffa9fb81e9539f
12 月 29 13:46:49 kernel: #PF: supervisor write access in kernel mode
12 月 29 13:46:49 kernel: #PF: error_code(0x0003) - permissions violation
12 月 29 13:46:49 kernel: PGD 100000067 P4D 100000067 PUD 1001c5067 PMD 12e469067 PTE 8000000115d7f161
12 月 29 13:46:49 kernel: Oops: 0003 [#1] SMP NOPTI
12 月 29 13:46:49 kernel: CPU: 1 PID: 143 Comm: kworker/1:2 Tainted: G           O      5.10.1-1-default #1 openSUSE Tumbleweed
12 月 29 13:46:49 kernel: Hardware name: LENOVO 20QNA00TCD/20QNA00TCD, BIOS N2NET41P (1.26 ) 10/27/2020
12 月 29 13:46:49 kernel: Workqueue: events request_firmware_work_func
12 月 29 13:46:49 kernel: RIP: 0010:iwl_dbg_tlv_alloc_region+0x27/0x180 [iwlwifi]
12 月 29 13:46:49 kernel: Code: 00 00 00 0f 1f 44 00 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 08 8b 46 04 44 8b 66 10 44 8b 6e 14 83 f8 3f 0f 86 0b 01 00 00 <c6> 46 37 00 48 89 fb 48 8b 7f 38 48 89 f5 4c 8d 4e 18 >
12 月 29 13:46:49 kernel: RSP: 0018:ffffa9fb803b3ce0 EFLAGS: 00010212
12 月 29 13:46:49 kernel: RAX: 0000000000000040 RBX: ffff8e4d26ab4018 RCX: 0000000000000000
12 月 29 13:46:49 kernel: RDX: ffffffffc12ad1b0 RSI: ffffa9fb81e95368 RDI: ffff8e4d26ab4018
12 月 29 13:46:49 kernel: RBP: 0000000000000000 R08: 0000000000000080 R09: 0000000000000001
12 月 29 13:46:49 kernel: R10: ffffa9fb81e953b0 R11: 0000000000000040 R12: 000000000000000c
12 月 29 13:46:49 kernel: R13: 0000000000000011 R14: ffff8e4d26abe000 R15: ffff8e4d052f8800
12 月 29 13:46:49 kernel: FS:  0000000000000000(0000) GS:ffff8e504c640000(0000) knlGS:0000000000000000
12 月 29 13:46:49 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
12 月 29 13:46:49 kernel: FS:  0000000000000000(0000) GS:ffff8e504c640000(0000) knlGS:0000000000000000
12 月 29 13:46:49 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
12 月 29 13:46:49 kernel: CR2: ffffa9fb81e9539f CR3: 0000000104070002 CR4: 00000000003706e0
12 月 29 13:46:49 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
12 月 29 13:46:49 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
12 月 29 13:46:49 kernel: Call Trace:
12 月 29 13:46:49 kernel:  iwl_dbg_tlv_alloc+0x79/0x120 [iwlwifi]
12 月 29 13:46:49 kernel:  iwl_req_fw_callback+0x10f0/0x2480 [iwlwifi]
12 月 29 13:46:49 kernel:  ? devres_add+0x1e/0x60
12 月 29 13:46:49 kernel:  ? fw_add_devm_name.part.0+0x5c/0x80
12 月 29 13:46:49 kernel:  ? assign_fw+0x6d/0x230
12 月 29 13:46:49 kernel:  request_firmware_work_func+0x4d/0x90
12 月 29 13:46:49 kernel:  process_one_work+0x1df/0x370
12 月 29 13:46:49 kernel:  worker_thread+0x50/0x400
12 月 29 13:46:49 kernel:  ? process_one_work+0x370/0x370
12 月 29 13:46:49 kernel:  kthread+0x11b/0x140
12 月 29 13:46:49 kernel:  ? __kthread_bind_mask+0x60/0x60
12 月 29 13:46:49 kernel:  ret_from_fork+0x1f/0x30
12 月 29 13:46:49 kernel: Modules linked in: fjes(-) vboxnetflt(O) iwlwifi uvcvideo videobuf2_vmalloc videobuf2_memops irqbypass videobuf2_v4l2 pcspkr videobuf2_common joydev efi_pstore soundwire_generic_allocation>
12 月 29 13:46:49 kernel:  sysfillrect sysimgblt fb_sys_fops cec nvme rc_core usbcore aesni_intel drm sdhci_pci glue_helper crypto_simd cqhci cryptd sdhci mmc_core serio_raw nvme_core wmi battery video pinctrl_cann>
12 月 29 13:46:49 kernel: CR2: ffffa9fb81e9539f
12 月 29 13:46:49 kernel: ---[ end trace fd71f7f778d11a84 ]---
12 月 29 13:46:49 kernel: RIP: 0010:iwl_dbg_tlv_alloc_region+0x27/0x180 [iwlwifi]
12 月 29 13:46:49 kernel: Code: 00 00 00 0f 1f 44 00 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 08 8b 46 04 44 8b 66 10 44 8b 6e 14 83 f8 3f 0f 86 0b 01 00 00 <c6> 46 37 00 48 89 fb 48 8b 7f 38 48 89 f5 4c 8d 4e 18 >
12 月 29 13:46:49 kernel: RSP: 0018:ffffa9fb803b3ce0 EFLAGS: 00010212
12 月 29 13:46:49 kernel: RAX: 0000000000000040 RBX: ffff8e4d26ab4018 RCX: 0000000000000000
12 月 29 13:46:49 kernel: RDX: ffffffffc12ad1b0 RSI: ffffa9fb81e95368 RDI: ffff8e4d26ab4018
12 月 29 13:46:49 kernel: RBP: 0000000000000000 R08: 0000000000000080 R09: 0000000000000001
12 月 29 13:46:49 kernel: R10: ffffa9fb81e953b0 R11: 0000000000000040 R12: 000000000000000c
12 月 29 13:46:49 kernel: R13: 0000000000000011 R14: ffff8e4d26abe000 R15: ffff8e4d052f8800
12 月 29 13:46:49 kernel: FS:  0000000000000000(0000) GS:ffff8e504c640000(0000) knlGS:0000000000000000
12 月 29 13:46:49 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
12 月 29 13:46:49 kernel: CR2: ffffa9fb81e9539f CR3: 0000000104070002 CR4: 00000000003706e0
12 月 29 13:46:49 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
12 月 29 13:46:49 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[无关部分省略]
12 月 29 13:47:48 kernel: BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 58s!
12 月 29 13:47:48 kernel: Showing busy workqueues and worker pools:
12 月 29 13:47:48 kernel: workqueue events: flags=0x0
12 月 29 13:47:48 kernel:   pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=12/256 refcnt=14
12 月 29 13:47:48 kernel:     in-flight: 885:request_firmware_work_func
12 月 29 13:47:48 kernel:     pending: delayed_fput, drm_fb_helper_dirty_work [drm_kms_helper], kernfs_notify_workfn, kfree_rcu_monitor, set_brightness_delayed BAR(880), deferred_probe_work_func, mei_cl_bus_rx_w>
12 月 29 13:47:48 kernel:   pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
12 月 29 13:47:48 kernel:     pending: vmstat_shepherd
12 月 29 13:47:48 kernel: workqueue events_long: flags=0x0
12 月 29 13:47:48 kernel:   pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
12 月 29 13:47:48 kernel:     in-flight: 223:ucsi_init_work [typec_ucsi]
12 月 29 13:47:48 kernel: workqueue events_unbound: flags=0x2
12 月 29 13:47:48 kernel:   pwq 16: cpus=0-7 flags=0x4 nice=0 active=4/512 refcnt=6
12 月 29 13:47:48 kernel:     in-flight: 59:fsnotify_connector_destroy_workfn fsnotify_connector_destroy_workfn, 61:fsnotify_mark_destroy_workfn fsnotify_mark_destroy_workfn
12 月 29 13:47:48 kernel: workqueue events_power_efficient: flags=0x80
12 月 29 13:47:48 kernel:   pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=3/256 refcnt=4
12 月 29 13:47:48 kernel:     pending: check_lifetime, sync_hw_clock, neigh_periodic_work
12 月 29 13:47:48 kernel: workqueue rcu_gp: flags=0x8
12 月 29 13:47:48 kernel:   pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=2/256 refcnt=3
12 月 29 13:47:48 kernel:     pending: process_srcu, wait_rcu_exp_gp
12 月 29 13:47:48 kernel: workqueue mm_percpu_wq: flags=0x8
12 月 29 13:47:48 kernel:   pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=2/256 refcnt=4
12 月 29 13:47:48 kernel:     pending: vmstat_update, lru_add_drain_per_cpu BAR(76)
12 月 29 13:47:48 kernel: workqueue kec_query: flags=0x0
12 月 29 13:47:48 kernel:   pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/16 refcnt=2
12 月 29 13:47:48 kernel:     pending: acpi_ec_event_processor
12 月 29 13:47:48 kernel: pool 0: cpus=0 node=0 flags=0x0 nice=0 hung=0s workers=4 idle: 752 7 5
12 月 29 13:47:48 kernel: pool 2: cpus=1 node=0 flags=0x0 nice=0 hung=58s workers=4 idle: 19 367 124
12 月 29 13:47:48 kernel: pool 16: cpus=0-7 flags=0x4 nice=0 hung=0s workers=9 idle: 60 8 62 63 933 64 58
12 月 29 13:47:52 kernel: ucsi_acpi USBC000:00: con2: failed to get status
12 月 29 13:48:20 kernel: BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 90s!
[无关部分省略]
1赞
2

不光是你，很多都遇到了。kernel 5.10 有很多严重 bug 。

3

TG 群顶置消息：

Intel AX200 网卡用户在升级到 5.10 内核后可能会遇到 workqueue lockup 导致无法启动的 bug，参见：
210733 – iwlwifi #PF at IP: 0010:iwl_dbg_tlv_alloc_region+0x27/0x180 [iwlwifi]
1180344 – iwlwifi: Kernel 5.10 fails to boot with workqueue lockup
目前可以通过在 /etc/modprobe.d/99-local.conf 中添加如下内容来解决：
options iwlwifi enable_ini=0
或者使用老内核启动。

4

但为啥 Live 镜像又是 OK 的呢？（虽然我已经开始重装了）

6

我也是遇见过几次 bug 后就只用 lts 了

7

可能是因为 Live CD 没有 kernel-firmware：

iwlwifi 驱动在 kernel-firmware 里：

2赞
8

本主题在最后一个回复创建后60分钟后自动锁定。不再允许添加新回复。