Open quantatic opened 3 years ago
Here's the relevant dmesg
output on 5.12.14
, produced with sudo airmon-ng start wlp5s0f3u3
.
[ 245.349032] INFO: task iw:2671 blocked for more than 122 seconds.
[ 245.349034] Tainted: P OE 5.12.14-arch1-1 #1
[ 245.349034] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.349035] task:iw state:D stack: 0 pid: 2671 ppid: 2670 flags:0x00000000
[ 245.349037] Call Trace:
[ 245.349038] __schedule+0x2ff/0x8b0
[ 245.349040] schedule+0x5b/0xc0
[ 245.349042] schedule_preempt_disabled+0x11/0x20
[ 245.349044] __mutex_lock.constprop.0+0x2f8/0x4e0
[ 245.349048] cfg80211_netdev_notifier_call+0x104/0x4f0 [cfg80211]
[ 245.349069] raw_notifier_call_chain+0x44/0x60
[ 245.349072] register_netdevice+0x4ee/0x5f0
[ 245.349075] cfg80211_rtw_set_default_mgmt_key+0x1f92/0x3f60 [88XXau]
[ 245.349107] nl80211_new_interface+0x1b5/0x4b0 [cfg80211]
[ 245.349129] genl_family_rcv_msg_doit+0xfd/0x160
[ 245.349132] genl_rcv_msg+0xeb/0x1e0
[ 245.349134] ? nl80211_get_interface+0x90/0x90 [cfg80211]
[ 245.349151] ? genl_get_cmd+0xd0/0xd0
[ 245.349153] netlink_rcv_skb+0x5b/0x100
[ 245.349155] genl_rcv+0x24/0x40
[ 245.349157] netlink_unicast+0x23e/0x350
[ 245.349159] netlink_sendmsg+0x23a/0x470
[ 245.349162] sock_sendmsg+0x5e/0x60
[ 245.349164] ____sys_sendmsg+0x258/0x2a0
[ 245.349166] ___sys_sendmsg+0xa3/0xf0
[ 245.349169] __sys_sendmsg+0x81/0xd0
[ 245.349171] do_syscall_64+0x33/0x40
[ 245.349173] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 245.349175] RIP: 0033:0x7f215203fcc7
[ 245.349176] RSP: 002b:00007fff4b050988 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
[ 245.349177] RAX: ffffffffffffffda RBX: 0000560d86945390 RCX: 00007f215203fcc7
[ 245.349178] RDX: 0000000000000000 RSI: 00007fff4b0509c0 RDI: 0000000000000003
[ 245.349178] RBP: 0000560d8694a8c0 R08: 0000560d869452a0 R09: 00007fff4b050a2c
[ 245.349179] R10: 00007fff4b050ca8 R11: 0000000000000246 R12: 0000560d8694a780
[ 245.349180] R13: 00007fff4b0509c0 R14: 0000560d8694a7d0 R15: 0000560d8694a8c0
[ 245.349182] INFO: task systemd-udevd:2672 blocked for more than 122 seconds.
[ 245.349184] Tainted: P OE 5.12.14-arch1-1 #1
[ 245.349185] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.349185] task:systemd-udevd state:D stack: 0 pid: 2672 ppid: 507 flags:0x00004220
[ 245.349187] Call Trace:
[ 245.349188] __schedule+0x2ff/0x8b0
[ 245.349191] schedule+0x5b/0xc0
[ 245.349193] schedule_preempt_disabled+0x11/0x20
[ 245.349195] __mutex_lock.constprop.0+0x2f8/0x4e0
[ 245.349196] ? netdev_name_node_lookup_rcu+0x67/0x80
[ 245.349198] dev_ioctl+0x182/0x4f0
[ 245.349201] sock_do_ioctl+0xee/0x190
[ 245.349204] sock_ioctl+0x278/0x360
[ 245.349207] __x64_sys_ioctl+0x82/0xb0
[ 245.349210] do_syscall_64+0x33/0x40
[ 245.349212] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 245.349213] RIP: 0033:0x7f7a5224259b
[ 245.349214] RSP: 002b:00007ffc0ebbf4b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 245.349215] RAX: ffffffffffffffda RBX: 0000562e978e8698 RCX: 00007f7a5224259b
[ 245.349216] RDX: 00007ffc0ebbf4c0 RSI: 0000000000008946 RDI: 0000000000000006
[ 245.349217] RBP: 00007ffc0ebbf668 R08: 0000000000000010 R09: 0000000000000001
[ 245.349218] R10: 00007f7a519168e8 R11: 0000000000000246 R12: 0000562e978f5c80
[ 245.349218] R13: 00007ffc0ebbf4c0 R14: 00007ffc0ebbf750 R15: 0000562e97ad9a90
I dig a bit of digging, and it seems this issue may be related to the changes made in https://github.com/torvalds/linux/commit/2fe8ef106238b274c505c480ecf00d8765abf0d8.
I have the same problem when using v5.6.4.2_35491.20191025
on Ubuntu 20.04.3 LTS
. If someone have a solution please comment.
same issue.
same issue
with the clue from @quantatic, I found that a similar issue (hang) on a different realtek driver rtw8852cu, can be solved by replacing register_netdevice
with cfg80211_register_netdevice
and unregister_netdevice
with cfg80211_unregister_netdevice
: https://github.com/ntzb/rtw8852cu/commit/891e3db8f525a6fb2d65e3ad928fd4a046e8d40a.
maybe it could be relevant in this case as well
I'm installing this driver via https://aur.archlinux.org/packages/rtl88xxau-aircrack-dkms-git, which appears to be installing the v5.6.4.2 branch, commit b8167e66b4ac046b3b76c2c40008d84528e91594.
When changing certain settings related to the network interface (for instance,
sudo airmon-ng start wlp5s0f3u3
results in a consistently reproducible error case), I get a variety of kernel errors viadmesg
, many of which result in full kernel lock-up (system calls and any other kernel-related API calls result in a permanent, uninterruptible, hang). I have tried two different WIFI USB devices (both with the same chipset), and both consistently produce the same error.This issue is consistently reproducible on
Arch Linux 5.12.14
, and consistently results in full kernel lock-up, requiring a hard reboot to resolve. I've also tested using the LTS kernel:Linux archlinux 5.10.47-1-lts #1 SMP Wed, 30 Jun 2021 13:52:19 +0000 x86_64 GNU/Linux
, and I also get a plethora of kernel errors, though it seems these errors are (at least not immediately) fatal, as the5.12.14
kernel errors appear to be. I've attached on such error below.This seems like it may be related to #498, though one comment in that thread claims that that issue was fixed.
Any advice for placed to start looking into the issue would be much appreciated. I'm happy to help track this issue down and resolve it, though I can't say I have too much kernel driver development experience :smiley: