You are not logged in.

#1 2023-12-10 08:58:49

hirak99
Member
Registered: 2023-11-04
Posts: 8

NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

The system can no longer shutdown or restart NetworkManager.service.

Just upgraded linux 6.6.5, everything was fine before this when I was running 6.6.2.

Device: Lenovo Legion 5 Pro Laptop
My network card: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter

This also prevents systemd from shutting down the system during `poweroff` (or `reboot`).

Is it a known issue? Is there anything I can try to pass to the kernel commandline to try to fix it?

Following is the excerpt from journal log until I was forced to shut down with the power button -

Dec 10 11:40:35 legion5pro systemd[1]: Stopping User Runtime Directory /run/user/1000...
Dec 10 11:40:35 legion5pro systemd[1]: run-user-1000.mount: Deactivated successfully.
Dec 10 11:40:35 legion5pro systemd[1]: Unmounted /run/user/1000.
Dec 10 11:40:35 legion5pro systemd[1]: user-runtime-dir@1000.service: Deactivated successfully.
Dec 10 11:40:35 legion5pro systemd[1]: Stopped User Runtime Directory /run/user/1000.
Dec 10 11:40:35 legion5pro systemd[1]: Removed slice User Slice of UID 1000.
Dec 10 11:40:35 legion5pro systemd[1]: user-1000.slice: Consumed 7.512s CPU time.
Dec 10 11:40:37 legion5pro sddm[917]: Display server stopped.
Dec 10 11:40:37 legion5pro sddm[917]: Running display stop script  ("/usr/share/sddm/scripts/Xstop")
Dec 10 11:40:37 legion5pro systemd[1]: sddm.service: Deactivated successfully.
Dec 10 11:40:37 legion5pro systemd[1]: Stopped Simple Desktop Display Manager.
Dec 10 11:40:37 legion5pro systemd[1]: sddm.service: Consumed 3.109s CPU time.
Dec 10 11:40:37 legion5pro systemd[1]: Stopping User Login Management...
Dec 10 11:40:37 legion5pro systemd[1]: Stopping Permit User Sessions...
Dec 10 11:40:37 legion5pro systemd[1]: systemd-user-sessions.service: Deactivated successfully.
Dec 10 11:40:37 legion5pro systemd[1]: Stopped Permit User Sessions.
Dec 10 11:40:37 legion5pro systemd[1]: systemd-logind.service: Deactivated successfully.
Dec 10 11:40:37 legion5pro systemd[1]: Stopped User Login Management.
Dec 10 11:40:37 legion5pro systemd[1]: Stopped target Network.
Dec 10 11:40:37 legion5pro systemd[1]: Stopped target Remote File Systems.
Dec 10 11:40:37 legion5pro systemd[1]: Stopping Network Manager...
Dec 10 11:40:37 legion5pro NetworkManager[724]: <info>  [1702188637.4550] caught SIGTERM, shutting down normally.
Dec 10 11:40:37 legion5pro systemd[1]: Stopping WPA supplicant...
Dec 10 11:40:37 legion5pro kernel: wlan0: deauthenticating from 8c:3b:ad:3d:05:05 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 10 11:40:37 legion5pro wpa_supplicant[906]: wlan0: CTRL-EVENT-DISCONNECTED bssid=8c:3b:ad:3d:05:05 reason=3 locally_generated=1
Dec 10 11:40:37 legion5pro NetworkManager[724]: <info>  [1702188637.5415] device (wlan0): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed')
Dec 10 11:40:37 legion5pro NetworkManager[724]: <info>  [1702188637.5420] manager: NetworkManager state is now DISCONNECTING
Dec 10 11:40:37 legion5pro dbus-daemon[706]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=724 comm="/usr/bin/NetworkManager --no-daemon")
Dec 10 11:40:37 legion5pro dbus-daemon[706]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down.
Dec 10 11:40:37 legion5pro NetworkManager[724]: <warn>  [1702188637.5438] dispatcher: (10) failed (after 0.001 sec): Refusing activation, D-Bus is shutting down.
Dec 10 11:40:37 legion5pro NetworkManager[724]: <info>  [1702188637.5439] device (wlan0): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed')
Dec 10 11:40:37 legion5pro NetworkManager[724]: <info>  [1702188637.5439] dhcp4 (wlan0): canceled DHCP transaction
Dec 10 11:40:37 legion5pro NetworkManager[724]: <info>  [1702188637.5439] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Dec 10 11:40:37 legion5pro NetworkManager[724]: <info>  [1702188637.5439] dhcp4 (wlan0): state changed no lease
Dec 10 11:40:37 legion5pro NetworkManager[724]: <info>  [1702188637.5440] dhcp6 (wlan0): canceled DHCP transaction
Dec 10 11:40:37 legion5pro NetworkManager[724]: <info>  [1702188637.5440] dhcp6 (wlan0): state changed no lease
Dec 10 11:42:07 legion5pro systemd[1]: wpa_supplicant.service: State 'stop-sigterm' timed out. Killing.
Dec 10 11:42:07 legion5pro systemd[1]: wpa_supplicant.service: Killing process 906 (wpa_supplicant) with signal SIGKILL.
Dec 10 11:42:07 legion5pro systemd[1]: NetworkManager.service: State 'stop-sigterm' timed out. Killing.
Dec 10 11:42:07 legion5pro systemd[1]: NetworkManager.service: Killing process 724 (NetworkManager) with signal SIGKILL.
Dec 10 11:42:07 legion5pro systemd-timesyncd[621]: Timed out waiting for reply from 192.46.210.39:123 (2.arch.pool.ntp.org).
Dec 10 11:42:18 legion5pro systemd-timesyncd[621]: Timed out waiting for reply from 95.216.144.226:123 (2.arch.pool.ntp.org).
Dec 10 11:42:28 legion5pro systemd-timesyncd[621]: Timed out waiting for reply from 192.46.212.117:123 (2.arch.pool.ntp.org).
Dec 10 11:42:38 legion5pro systemd-timesyncd[621]: Timed out waiting for reply from 139.59.55.93:123 (2.arch.pool.ntp.org).
Dec 10 11:43:37 legion5pro systemd[1]: wpa_supplicant.service: Processes still around after SIGKILL. Ignoring.
Dec 10 11:43:37 legion5pro systemd[1]: NetworkManager.service: Processes still around after SIGKILL. Ignoring.
Dec 10 11:43:44 legion5pro kernel: INFO: task kworker/u32:1:12 blocked for more than 122 seconds.
Dec 10 11:43:44 legion5pro kernel:       Tainted: P           OE      6.6.5-arch1-1 #1
Dec 10 11:43:44 legion5pro kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 10 11:43:44 legion5pro kernel: task:kworker/u32:1   state:D stack:0     pid:12    ppid:2      flags:0x00004000
Dec 10 11:43:44 legion5pro kernel: Workqueue: events_power_efficient reg_check_chans_work [cfg80211]
Dec 10 11:43:44 legion5pro kernel: Call Trace:
Dec 10 11:43:44 legion5pro kernel:  <TASK>
Dec 10 11:43:44 legion5pro kernel:  __schedule+0x3e7/0x1410
Dec 10 11:43:44 legion5pro kernel:  schedule+0x5e/0xd0
Dec 10 11:43:44 legion5pro kernel:  schedule_preempt_disabled+0x15/0x30
Dec 10 11:43:44 legion5pro kernel:  __mutex_lock.constprop.0+0x39a/0x6a0
Dec 10 11:43:44 legion5pro kernel:  ? finish_task_switch.isra.0+0x94/0x2f0
Dec 10 11:43:44 legion5pro kernel:  reg_check_chans_work+0x31/0x5b0 [cfg80211 59703855bef4bd361ba426fe3ab0391c26f6ec0e]
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  process_one_work+0x174/0x340
Dec 10 11:43:44 legion5pro kernel:  worker_thread+0x27b/0x3a0
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_worker_thread+0x10/0x10
Dec 10 11:43:44 legion5pro kernel:  kthread+0xe8/0x120
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_kthread+0x10/0x10
Dec 10 11:43:44 legion5pro kernel:  ret_from_fork+0x34/0x50
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_kthread+0x10/0x10
Dec 10 11:43:44 legion5pro kernel:  ret_from_fork_asm+0x1b/0x30
Dec 10 11:43:44 legion5pro kernel:  </TASK>
Dec 10 11:43:44 legion5pro kernel: INFO: task kworker/8:2:275 blocked for more than 122 seconds.
Dec 10 11:43:44 legion5pro kernel:       Tainted: P           OE      6.6.5-arch1-1 #1
Dec 10 11:43:44 legion5pro kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 10 11:43:44 legion5pro kernel: task:kworker/8:2     state:D stack:0     pid:275   ppid:2      flags:0x00004000
Dec 10 11:43:44 legion5pro kernel: Workqueue: events disconnect_work [cfg80211]
Dec 10 11:43:44 legion5pro kernel: Call Trace:
Dec 10 11:43:44 legion5pro kernel:  <TASK>
Dec 10 11:43:44 legion5pro kernel:  __schedule+0x3e7/0x1410
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? __wake_up_common_lock+0x8f/0xd0
Dec 10 11:43:44 legion5pro kernel:  schedule+0x5e/0xd0
Dec 10 11:43:44 legion5pro kernel:  schedule_preempt_disabled+0x15/0x30
Dec 10 11:43:44 legion5pro kernel:  __mutex_lock.constprop.0+0x39a/0x6a0
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  disconnect_work+0x16/0xd0 [cfg80211 59703855bef4bd361ba426fe3ab0391c26f6ec0e]
Dec 10 11:43:44 legion5pro kernel:  process_one_work+0x174/0x340
Dec 10 11:43:44 legion5pro kernel:  worker_thread+0x27b/0x3a0
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_worker_thread+0x10/0x10
Dec 10 11:43:44 legion5pro kernel:  kthread+0xe8/0x120
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_kthread+0x10/0x10
Dec 10 11:43:44 legion5pro kernel:  ret_from_fork+0x34/0x50
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_kthread+0x10/0x10
Dec 10 11:43:44 legion5pro kernel:  ret_from_fork_asm+0x1b/0x30
Dec 10 11:43:44 legion5pro kernel:  </TASK>
Dec 10 11:43:44 legion5pro kernel: INFO: task NetworkManager:724 blocked for more than 122 seconds.
Dec 10 11:43:44 legion5pro kernel:       Tainted: P           OE      6.6.5-arch1-1 #1
Dec 10 11:43:44 legion5pro kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 10 11:43:44 legion5pro kernel: task:NetworkManager  state:D stack:0     pid:724   ppid:1      flags:0x00000006
Dec 10 11:43:44 legion5pro kernel: Call Trace:
Dec 10 11:43:44 legion5pro kernel:  <TASK>
Dec 10 11:43:44 legion5pro kernel:  __schedule+0x3e7/0x1410
Dec 10 11:43:44 legion5pro kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Dec 10 11:43:44 legion5pro kernel:  schedule+0x5e/0xd0
Dec 10 11:43:44 legion5pro kernel:  schedule_preempt_disabled+0x15/0x30
Dec 10 11:43:44 legion5pro kernel:  __mutex_lock.constprop.0+0x39a/0x6a0
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  nl80211_pre_doit+0x14f/0x250 [cfg80211 59703855bef4bd361ba426fe3ab0391c26f6ec0e]
Dec 10 11:43:44 legion5pro kernel:  genl_family_rcv_msg_doit+0xdd/0x150
Dec 10 11:43:44 legion5pro kernel:  genl_rcv_msg+0x1b3/0x2c0
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211 59703855bef4bd361ba426fe3ab0391c26f6ec0e]
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_nl80211_get_interface+0x10/0x10 [cfg80211 59703855bef4bd361ba426fe3ab0391c26f6ec0e]
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_nl80211_post_doit+0x10/0x10 [cfg80211 59703855bef4bd361ba426fe3ab0391c26f6ec0e]
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_genl_rcv_msg+0x10/0x10
Dec 10 11:43:44 legion5pro kernel:  netlink_rcv_skb+0x5b/0x110
Dec 10 11:43:44 legion5pro kernel:  genl_rcv+0x28/0x40
Dec 10 11:43:44 legion5pro kernel:  netlink_unicast+0x1a6/0x290
Dec 10 11:43:44 legion5pro kernel:  netlink_sendmsg+0x254/0x4d0
Dec 10 11:43:44 legion5pro kernel:  ____sys_sendmsg+0x399/0x3d0
Dec 10 11:43:44 legion5pro kernel:  ? copy_msghdr_from_user+0x7d/0xc0
Dec 10 11:43:44 legion5pro kernel:  ___sys_sendmsg+0x9a/0xe0
Dec 10 11:43:44 legion5pro kernel:  __sys_sendmsg+0x7a/0xd0
Dec 10 11:43:44 legion5pro kernel:  do_syscall_64+0x60/0x90
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? do_syscall_64+0x6c/0x90
Dec 10 11:43:44 legion5pro kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Dec 10 11:43:44 legion5pro kernel: RIP: 0033:0x7f7d88f5db3d
Dec 10 11:43:44 legion5pro kernel: RSP: 002b:00007ffc2aecc940 EFLAGS: 00000293 ORIG_RAX: 000000000000002e
Dec 10 11:43:44 legion5pro kernel: RAX: ffffffffffffffda RBX: 000055f7b15483e0 RCX: 00007f7d88f5db3d
Dec 10 11:43:44 legion5pro kernel: RDX: 0000000000000000 RSI: 00007ffc2aecc980 RDI: 000000000000000b
Dec 10 11:43:44 legion5pro kernel: RBP: 00007ffc2aecca10 R08: 0000000000000000 R09: 0000000000000001
Dec 10 11:43:44 legion5pro kernel: R10: 0000000000000003 R11: 0000000000000293 R12: 000055f7b160ff90
Dec 10 11:43:44 legion5pro kernel: R13: 000055f7b15483e0 R14: 000055f7b15e60d0 R15: 000000000000000a
Dec 10 11:43:44 legion5pro kernel:  </TASK>
Dec 10 11:43:44 legion5pro kernel: INFO: task wpa_supplicant:906 blocked for more than 122 seconds.
Dec 10 11:43:44 legion5pro kernel:       Tainted: P           OE      6.6.5-arch1-1 #1
Dec 10 11:43:44 legion5pro kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 10 11:43:44 legion5pro kernel: task:wpa_supplicant  state:D stack:0     pid:906   ppid:1      flags:0x00004006
Dec 10 11:43:44 legion5pro kernel: Call Trace:
Dec 10 11:43:44 legion5pro kernel:  <TASK>
Dec 10 11:43:44 legion5pro kernel:  __schedule+0x3e7/0x1410
Dec 10 11:43:44 legion5pro kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Dec 10 11:43:44 legion5pro kernel:  schedule+0x5e/0xd0
Dec 10 11:43:44 legion5pro kernel:  schedule_preempt_disabled+0x15/0x30
Dec 10 11:43:44 legion5pro kernel:  __mutex_lock.constprop.0+0x39a/0x6a0
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? __nla_reserve+0x3c/0x50
Dec 10 11:43:44 legion5pro kernel:  nl80211_send_iface+0x25b/0x980 [cfg80211 59703855bef4bd361ba426fe3ab0391c26f6ec0e]
Dec 10 11:43:44 legion5pro kernel:  ? kmalloc_reserve+0x62/0xf0
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? __alloc_skb+0xde/0x1a0
Dec 10 11:43:44 legion5pro kernel:  nl80211_get_interface+0x4f/0xa0 [cfg80211 59703855bef4bd361ba426fe3ab0391c26f6ec0e]
Dec 10 11:43:44 legion5pro kernel:  genl_family_rcv_msg_doit+0xf2/0x150
Dec 10 11:43:44 legion5pro kernel:  genl_rcv_msg+0x1b3/0x2c0
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211 59703855bef4bd361ba426fe3ab0391c26f6ec0e]
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_nl80211_get_interface+0x10/0x10 [cfg80211 59703855bef4bd361ba426fe3ab0391c26f6ec0e]
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_nl80211_post_doit+0x10/0x10 [cfg80211 59703855bef4bd361ba426fe3ab0391c26f6ec0e]
Dec 10 11:43:44 legion5pro kernel:  ? __pfx_genl_rcv_msg+0x10/0x10
Dec 10 11:43:44 legion5pro kernel:  netlink_rcv_skb+0x5b/0x110
Dec 10 11:43:44 legion5pro kernel:  genl_rcv+0x28/0x40
Dec 10 11:43:44 legion5pro kernel:  netlink_unicast+0x1a6/0x290
Dec 10 11:43:44 legion5pro kernel:  netlink_sendmsg+0x254/0x4d0
Dec 10 11:43:44 legion5pro kernel:  ____sys_sendmsg+0x399/0x3d0
Dec 10 11:43:44 legion5pro kernel:  ? copy_msghdr_from_user+0x7d/0xc0
Dec 10 11:43:44 legion5pro kernel:  ___sys_sendmsg+0x9a/0xe0
Dec 10 11:43:44 legion5pro kernel:  __sys_sendmsg+0x7a/0xd0
Dec 10 11:43:44 legion5pro kernel:  do_syscall_64+0x60/0x90
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? do_syscall_64+0x6c/0x90
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? do_syscall_64+0x6c/0x90
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? do_syscall_64+0x6c/0x90
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Dec 10 11:43:44 legion5pro kernel:  ? srso_alias_return_thunk+0x5/0x7f
Dec 10 11:43:44 legion5pro kernel:  ? do_syscall_64+0x6c/0x90
Dec 10 11:43:44 legion5pro kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Dec 10 11:43:44 legion5pro kernel: RIP: 0033:0x7f7b20530b04
Dec 10 11:43:44 legion5pro kernel: RSP: 002b:00007ffc4d073dc8 EFLAGS: 00000202 ORIG_RAX: 000000000000002e
Dec 10 11:43:44 legion5pro kernel: RAX: ffffffffffffffda RBX: 0000560e9f8469d0 RCX: 00007f7b20530b04
Dec 10 11:43:44 legion5pro kernel: RDX: 0000000000000000 RSI: 00007ffc4d073e00 RDI: 0000000000000006
Dec 10 11:43:44 legion5pro kernel: RBP: 0000560e9f8d0580 R08: 0000000000000004 R09: 0000000000000001
Dec 10 11:43:44 legion5pro kernel: R10: 00007ffc4d073ee0 R11: 0000000000000202 R12: 0000560e9f846cb0
Dec 10 11:43:44 legion5pro kernel: R13: 00007ffc4d073e00 R14: 0000560e9f192170 R15: 00007ffc4d073ee0
Dec 10 11:43:44 legion5pro kernel:  </TASK>
Dec 10 11:45:07 legion5pro systemd[1]: wpa_supplicant.service: State 'final-sigterm' timed out. Killing.
Dec 10 11:45:07 legion5pro systemd[1]: wpa_supplicant.service: Killing process 906 (wpa_supplicant) with signal SIGKILL.
Dec 10 11:45:08 legion5pro systemd[1]: NetworkManager.service: State 'final-sigterm' timed out. Killing.
Dec 10 11:45:08 legion5pro systemd[1]: NetworkManager.service: Killing process 724 (NetworkManager) with signal SIGKILL.
Dec 10 11:45:47 legion5pro kernel: INFO: task kworker/u32:1:12 blocked for more than 245 seconds.
Dec 10 11:45:47 legion5pro kernel:       Tainted: P           OE      6.6.5-arch1-1 #1
Dec 10 11:45:47 legion5pro kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 10 11:45:47 legion5pro kernel: task:kworker/u32:1   state:D stack:0     pid:12    ppid:2      flags:0x00004000
Dec 10 11:45:47 legion5pro kernel: Workqueue: events_power_efficient reg_check_chans_work [cfg80211]
Dec 10 11:45:47 legion5pro kernel: Call Trace:
Dec 10 11:45:47 legion5pro kernel:  <TASK>
Dec 10 11:45:47 legion5pro kernel:  __schedule+0x3e7/0x1410

Offline

#2 2023-12-10 09:12:55

hirak99
Member
Registered: 2023-11-04
Posts: 8

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

I just tried linux-lts, which is 6.1.66. To my surprise the issue persists. Does this mean there's something wrong with the chipset itself?

This started after I installed linux 6.6.5 today.

Offline

#3 2023-12-10 10:02:49

nium
Member
Registered: 2018-03-21
Posts: 1

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Same behaviour here on my AMD system. No poweroff or reboot is possible for standard linux or linux-lts kernel.
NIC: Realtek Semiconductor Co., Ltd. RTL8812AE 802.11ac PCIe Wireless Network Adapter
CPU: AMD RYZEN 7
CHIPSET: B550

Last edited by nium (2023-12-10 20:18:36)

Offline

#4 2023-12-10 10:43:37

laminarde
Member
Registered: 2023-12-10
Posts: 3

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Same here running zen kernel 6.5.5 on framework 13 amd.

Shutdown fails, hibernate will cut off wifi.   

Rollback to linux-6.5.5-zen solves the issue for me.

journalctl shows

Freezing user space processes failed after 20.008 seconds (8 tasks refusing to freeze, wq_busy=0)

Among others, wpa_supplicant and DNS are affected.

Offline

#5 2023-12-10 10:58:00

VoDo
Member
From: Europe
Registered: 2020-06-04
Posts: 122

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Same here (It refused to start network manager and stuck on start)I can not even go back to 6.6.2.
kworker/u8:2:84 blocked when try pacman -U that kernel


edit
I disabled NetworkManager
reboot>pacman - U 6.6.2 linux with headers
reboot>enable NetworkManager
it works again

Last edited by VoDo (2023-12-10 11:28:55)


Archi3

Offline

#6 2023-12-10 11:33:51

xerxes_
Member
Registered: 2018-04-29
Posts: 675

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Do you all use WiFi connection? What network cards & drivers do you use?

You may check by 'systemctl list-unit-files --state enabled' if you don't use multiple network services which may colflict.

Last edited by xerxes_ (2023-12-10 11:37:19)

Offline

#7 2023-12-10 11:44:44

VoDo
Member
From: Europe
Registered: 2020-06-04
Posts: 122

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

I do yes broadcom-wl-dkms


Archi3

Offline

#8 2023-12-10 12:03:41

loqs
Member
Registered: 2014-03-06
Posts: 17,337

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

VoDo wrote:

I do yes broadcom-wl-dkms

https://gitlab.archlinux.org/archlinux/ … -/issues/1

@hirak99 and possibly @laminarde does reverting https://github.com/archlinux/linux/comm … ee05662f57 make any difference on your system?
@laminarde what NIC is your system using and what kernel module?

Offline

#9 2023-12-10 12:17:36

VoDo
Member
From: Europe
Registered: 2020-06-04
Posts: 122

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

loqs wrote:
VoDo wrote:

I do yes broadcom-wl-dkms

https://gitlab.archlinux.org/archlinux/ … -/issues/1

@hirak99 and possibly @laminarde does reverting https://github.com/archlinux/linux/comm … ee05662f57 make any difference on your system?
@laminarde what NIC is your system using and what kernel module?

Thank you, I use an old MacBook Air 11" 2013 apple abandoned it years ago Arch gave it a new life.


Archi3

Offline

#10 2023-12-10 13:51:41

Sardo
Member
Registered: 2023-12-10
Posts: 1

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Ditto on my  MacBookPro12,1 w/Broadcom BCM43602 & Broadcom NetXtreme BCM57762
hangs with 6.6.5-arch1-1
reverted to 6.6.4-arch1-1 to resolve.

Offline

#11 2023-12-10 14:50:06

laminarde
Member
Registered: 2023-12-10
Posts: 3

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

loqs wrote:

@laminarde what NIC is your system using and what kernel module?

The wifi card is reported as mt7922e.

sudo lspci -vnn

01:00.0 Network controller [0280]: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:0616]
    Subsystem: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:e616]
    Flags: bus master, fast devsel, latency 0, IRQ 116, IOMMU group 1
    Memory at 7c10900000 (64-bit, prefetchable) [size=1M]
    Memory at 90b00000 (64-bit, non-prefetchable) [size=32K]
    Capabilities: [80] Express Endpoint, MSI 00
    Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+
    Capabilities: [f8] Power Management version 3
    Kernel driver in use: mt7921e
    Kernel modules: mt7921e

sudo dmesg

[   19.713216] mt7921e 0000:01:00.0: enabling device (0000 -> 0002)
[   19.717453] mt7921e 0000:01:00.0: ASIC revision: 79220010
[   19.788657] mt7921e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20230627143702a
[   20.162683] mt7921e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20230627143946

Offline

#12 2023-12-10 16:36:15

chiiydd
Member
Registered: 2023-12-10
Posts: 1

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Same behavior too.
Downgrade  linux back to  6.6.4-arch1-1 to resolve.
My CPU:AMD 7840HS.My network card is also MT7922.

Offline

#13 2023-12-10 16:41:14

loqs
Member
Registered: 2014-03-06
Posts: 17,337

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Could someone using the mt7921e try reverting https://github.com/archlinux/linux/comm … ee05662f57  If it helps the kernel linked below has been built with that commit reverted:

https://drive.google.com/file/d/1Icy2Oj … sp=sharing linux-6.6.5.arch1-1.1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1Iv_BMY … sp=sharing linux-headers-6.6.5.arch1-1.1-x86_64.pkg.tar.zst

Offline

#14 2023-12-10 17:04:45

hirak99
Member
Registered: 2023-11-04
Posts: 8

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

loqs wrote:

Could someone using the mt7921e try reverting https://github.com/archlinux/linux/comm … ee05662f57  If it helps the kernel linked below has been built with that commit reverted:

https://drive.google.com/file/d/1Icy2Oj … sp=sharing linux-6.6.5.arch1-1.1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1Iv_BMY … sp=sharing linux-headers-6.6.5.arch1-1.1-x86_64.pkg.tar.zst

I confirm this resolves the issue for me!

I installed the packages you built from your links, and it reboots and powers off without problem.

PS. To be clear, I have MT7922 with this issue (not mt7921e) Edit: which is found is using mt7921e (post below).

Last edited by hirak99 (2023-12-10 17:51:25)

Offline

#15 2023-12-10 17:10:57

loqs
Member
Registered: 2014-03-06
Posts: 17,337

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

@hirak99 what kernel module is your system using for the MT7922?  You can check in the output of `lspci -v`.

Offline

#16 2023-12-10 17:50:16

hirak99
Member
Registered: 2023-11-04
Posts: 8

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

loqs wrote:

@hirak99 what kernel module is your system using for the MT7922?  You can check in the output of `lspci -v`.

It's using mt7921e.

$ sudo lspci -v
...
03:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
        DeviceName: Realtek
        Subsystem: Lenovo MT7922 802.11ax PCI Express Wireless Network Adapter
        Flags: bus master, fast devsel, latency 0, IRQ 109, IOMMU group 16
        Memory at 8038000000 (64-bit, prefetchable) [size=1M]
        Memory at b9b00000 (64-bit, non-prefetchable) [size=32K]
        Capabilities: [80] Express Endpoint, MSI 00
        Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+
        Capabilities: [f8] Power Management version 3
        Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
        Capabilities: [108] Latency Tolerance Reporting
        Capabilities: [110] L1 PM Substates
        Capabilities: [200] Advanced Error Reporting
        Kernel driver in use: mt7921e
        Kernel modules: mt7921e
...

Offline

#17 2023-12-10 18:41:49

laminarde
Member
Registered: 2023-12-10
Posts: 3

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

loqs wrote:

Could someone using the mt7921e try reverting https://github.com/archlinux/linux/comm … ee05662f57

Reverting that commit fixes the issue for me (linux-zen). I had to learn that you can't get commits from a remote git repo, ouch.

Thanks for your help loqs.

Offline

#18 2023-12-10 19:52:12

KeNaCo
Member
Registered: 2012-11-01
Posts: 18

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Same issue. Revert to 6.6.4 is not working (graphics issue, unrelated to this thread), but I suggest disabling NetworkManager service in such cases. The system will be without internet but functional under 6.6.5

If it helps someone investigating impacted HW:

lspci | grep Network
05:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360  802.11ac Dual Band Wireless Network Adapter (rev 03)

Last edited by KeNaCo (2023-12-10 19:53:43)

Offline

#19 2023-12-10 19:54:53

pavlosdec
Member
Registered: 2019-03-10
Posts: 18

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Same problem here. The whole system hangs when rebooting or shutting down. Downgrading linux and linux-headers to 6.6.4 solves the issue.

Offline

#20 2023-12-10 20:17:30

nicools
Member
Registered: 2023-12-10
Posts: 1

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Same issue. Reverting to 6.6.4 solved the problem as some posts suggested.
Using module mt7921e.

 29:00.0 Network controller [0280]: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz [14c3:0608]
	Subsystem: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz [14c3:0608]
	Flags: bus master, fast devsel, latency 0, IRQ 92, IOMMU group 13
	Memory at 7c30300000 (64-bit, prefetchable) [size=1M]
	Memory at 7c30400000 (64-bit, prefetchable) [size=16K]
	Memory at 7c30404000 (64-bit, prefetchable) [size=4K]
	Capabilities: [80] Express Endpoint, MSI 00
	Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+
	Capabilities: [f8] Power Management version 3
	Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
	Capabilities: [108] Latency Tolerance Reporting
	Capabilities: [110] L1 PM Substates
	Capabilities: [200] Advanced Error Reporting
	Kernel driver in use: mt7921e
	Kernel modules: mt7921e 
hirak99 wrote:

I just tried linux-lts, which is 6.1.66. To my surprise the issue persists. Does this mean there's something wrong with the chipset itself?

The same happened to me. Only when reverting to 6.6.4 my system was able to shutdown normally.

Offline

#21 2023-12-10 21:04:28

mozlima
Member
Registered: 2019-09-22
Posts: 8

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Having problem with Realtek chipset

Bus 001 Device 003: ID 0bda:c811 Realtek Semiconductor Corp. 802.11ac NIC

Every tool related to wifi freezes
usb_modeswitch, iw dev, sudo dmesg, iwd network manager+iwd, network manager+wpa_supplicant

Reverting to linux-6.6.4.arch1-1 and linux-headers-6.6.4.arch1-1 fix the problem

Im using:

https://aur.archlinux.org/packages/rtl8 … r-dkms-git


Bug report:
https://github.com/morrownr/8821cu-20210916/issues/131

Does anyone know if this is related to this thread?

Last edited by mozlima (2023-12-10 21:18:59)

Offline

#22 2023-12-10 21:34:12

xerxes_
Member
Registered: 2018-04-29
Posts: 675

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Maybe post some more logs from crashed boots: 'sudo journalctl -b'?

Last edited by xerxes_ (2023-12-20 17:11:06)

Offline

#23 2023-12-10 21:52:32

loqs
Member
Registered: 2014-03-06
Posts: 17,337

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

@mozlima the back trace from your report against 8821cu-20210916 looks very different to hung task back trace from https://bugzilla.kernel.org/show_bug.cgi?id=218247
Edit:
Have you tried reverting https://github.com/archlinux/linux/comm … ee05662f57?  See https://bbs.archlinux.org/viewtopic.php … 3#p2136473 for a kernel I built for that purpose.

Last edited by loqs (2023-12-10 21:55:28)

Offline

#24 2023-12-10 22:03:48

ndavid
Member
Registered: 2021-04-24
Posts: 21

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

Sardo wrote:

Ditto on my  MacBookPro12,1 w/Broadcom BCM43602 & Broadcom NetXtreme BCM57762
hangs with 6.6.5-arch1-1
reverted to 6.6.4-arch1-1 to resolve.

Hey, I'm having the same problem but on a MediaTek. May I ask which commands you used to downgrade your kernel? (And I'm on nvidia-dkms, does it matter?)

Offline

#25 2023-12-10 22:13:31

leoetlino
Member
Registered: 2023-12-10
Posts: 1

Re: NetworkManager won't shutdown, hangs kworker - after linux 6.6.5

This is a kernel bug on the 6.6.x stable branch. As people have correctly pointed out, 4a7e92551618 ("wifi: cfg80211: fix CQM for non-range use" backported to 6.6.x) is the culprit as it causes cfg80211_cqm_rssi_update not to release the wdev lock in some cases - which then causes various other things to deadlock.

I have submitted a patch: https://lore.kernel.org/stable/20231210 … olam.fr/T/

I'm pretty sure it will fix the issue but I haven't tested it.

Offline

Board footer

Powered by FluxBB