Bug 78991
| Summary: | rtl8723be: connection hangs frequently, until rtl_watchdog_wq_callback() causes reconnect and/or kernel oops | ||
|---|---|---|---|
| Product: | Networking | Reporter: | Chí-Thanh Christopher Nguyễn (chithanh) |
| Component: | Wireless | Assignee: | networking_wireless (networking_wireless) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | Larry.Finger, linville |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 3.15.0 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | dmesg | ||
Created attachment 141001 [details] dmesg When receiving many packets, the connection will frequently hang. A few seconds after that, I get the following message in dmesg: rtlwifi:rtl_watchdog_wq_callback():<0-0> AP off, try to reconnect now Sending packets, or light incoming traffic (such as ping at 1 second interval) seems not to trigger the problem. In addition, I am sometimes seeing an oops when that happens. But not regularly, on some days I don't see it at all: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 3271 at kernel/softirq.c:146 __local_bh_enable_ip+0x62/0x90() Modules linked in: vfat fat uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core btusb kvm rtl8723be btcoexist rtl_pci rtlwifi rtl8723_common CPU: 1 PID: 3271 Comm: wpa_supplicant Not tainted 3.15.0-gentoo-r1 #2 Hardware name: MEDION AKOYA E1318T/AKOYA E1318T, BIOS 210 08/07/2013 0000000000000009 ffff8800a9957720 ffffffff81882cca 0000000000000000 ffff8800a9957758 ffffffff81074a78 0000000000000200 ffffffff81ead540 ffffffffa0021ad0 000000000000005e ffff8800bdecd980 ffff8800a9957768 Call Trace: [<ffffffff81882cca>] dump_stack+0x45/0x56 [<ffffffff81074a78>] warn_slowpath_common+0x78/0xa0 [<ffffffffa0021ad0>] ? rtl_pci_reset_trx_ring+0x1c0/0x250 [rtl_pci] [<ffffffff81074b55>] warn_slowpath_null+0x15/0x20 [<ffffffff81079902>] __local_bh_enable_ip+0x62/0x90 [<ffffffff816d85ba>] destroy_conntrack+0x6a/0xb0 [<ffffffff816d4062>] nf_conntrack_destroy+0x12/0x20 [<ffffffff81696c75>] skb_release_head_state+0x85/0xd0 [<ffffffff81697c5d>] skb_release_all+0xd/0x30 [<ffffffff81697cd2>] kfree_skb+0x32/0x80 [<ffffffffa0021ad0>] rtl_pci_reset_trx_ring+0x1c0/0x250 [rtl_pci] [<ffffffffa001074a>] rtl_ps_enable_nic+0x7a/0xc0 [rtlwifi] [<ffffffffa00489bf>] rtl8723be_phy_set_rf_power_state+0x4ff/0x780 [rtl8723be] [<ffffffffa00100d3>] rtl_ps_set_rf_state+0x33/0xf0 [rtlwifi] [<ffffffffa00101c6>] _rtl_ps_inactive_ps+0x36/0xc0 [rtlwifi] [<ffffffffa0010864>] rtl_ips_nic_on+0x84/0xb0 [rtlwifi] [<ffffffffa000da10>] rtl_op_config+0x2c0/0x3d0 [rtlwifi] [<ffffffff8182ed43>] ieee80211_hw_config+0x73/0x350 [<ffffffff8184002d>] ieee80211_recalc_idle+0x1d/0x20 [<ffffffff81835cc4>] __ieee80211_start_scan+0x134/0x530 [<ffffffff81836b0b>] ieee80211_request_scan+0x2b/0x50 [<ffffffff81844f13>] ieee80211_scan+0x63/0xb0 [<ffffffff81813cc2>] nl80211_trigger_scan+0x5c2/0x680 [<ffffffff816d3a79>] genl_family_rcv_msg+0x199/0x380 [<ffffffff816d3c60>] ? genl_family_rcv_msg+0x380/0x380 [<ffffffff816d3ce9>] genl_rcv_msg+0x89/0xd0 [<ffffffff816d1e49>] netlink_rcv_skb+0xa9/0xc0 [<ffffffff816d2313>] genl_rcv+0x23/0x40 [<ffffffff816d17a8>] netlink_unicast+0x158/0x240 [<ffffffff816d1b87>] netlink_sendmsg+0x2f7/0x400 [<ffffffff8168ea66>] sock_sendmsg+0x86/0xc0 [<ffffffff8168e7a9>] ? move_addr_to_kernel.part.20+0x19/0x60 [<ffffffff8168f4f9>] ? move_addr_to_kernel+0x19/0x30 [<ffffffff8168ee53>] ___sys_sendmsg+0x373/0x380 [<ffffffff81186511>] ? set_fd_set+0x21/0x30 [<ffffffff811883ba>] ? __d_free+0x3a/0x60 [<ffffffff8168d9a4>] ? move_addr_to_user+0xb4/0xd0 [<ffffffff8118f03e>] ? __fdget+0xe/0x10 [<ffffffff810c98d3>] ? ktime_get_ts+0x43/0xe0 [<ffffffff811865fc>] ? poll_select_copy_remaining+0xdc/0x130 [<ffffffff8168fbad>] __sys_sendmsg+0x3d/0x80 [<ffffffff8168fbfd>] SyS_sendmsg+0xd/0x20 [<ffffffff81894262>] system_call_fastpath+0x16/0x1b ---[ end trace 510d53a178674ab9 ]--- As I find several reports on the Internet about similar oopses in other rtlwifi drivers, it may be not strictly related to the rtl8723be.