Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Network Adapter Dies Randomly
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
justin_brody
Apprentice
Apprentice


Joined: 26 Jan 2005
Posts: 221

PostPosted: Mon Apr 15, 2019 7:42 pm    Post subject: Network Adapter Dies Randomly Reply with quote

Hello,
I've been having a strange issue with my wireless adapter for the past week or so. The device works fine and then at some point it randomly stops working -- I show 0 bars in my NetworkManager applet; if I type
Code:
ifconfig wlan0 up

after taking it down it say no such device.

The card is an Intel® Centrino® Ultimate-N 6300. After it crashes the drivers (iwlwifi and iwldvm) are still running; removing them and putting them back in (with modprobe) doesn't seem to help. Rebooting the machine gives me the drivers back.

I was running a 4.9.x kernel and just upgraded to 4.19.27 to see if that helped.

I'm also running some virtualbox modules:
Code:


 # lsmod
Module                  Size  Used by
vboxpci                28672  0
vboxnetadp             28672  0
x86_pkg_temp_thermal    16384  0
vboxnetflt             32768  0
vboxdrv               421888  3 vboxpci,vboxnetadp,vboxnetflt
iwldvm                147456  0
iwlwifi               221184  1 iwldvm


I do see some errors in /var/log/messages, but I think these are from when I restarted
Code:


Apr 15 15:20:28 maya kernel: iwlwifi 0000:03:00.0: Error sending REPLY_ADD_STA: time out after 2000ms.
Apr 15 15:20:28 maya kernel: iwlwifi 0000:03:00.0: Current CMD queue read_ptr 154 write_ptr 159
Apr 15 15:20:28 maya kernel: ------------[ cut here ]------------
Apr 15 15:20:28 maya kernel: Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff)
Apr 15 15:20:28 maya kernel: WARNING: CPU: 0 PID: 25508 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2009 iwl_trans_pcie_grab_nic_access+0x176/0x210 [iwlwifi]
Apr 15 15:20:28 maya kernel: Modules linked in: vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) iwldvm x86_pkg_temp_thermal iwlwifi


Any ideas about how I could fix this or debug more?

Thanks in advance!
[/code]
Back to top
View user's profile Send private message
justin_brody
Apprentice
Apprentice


Joined: 26 Jan 2005
Posts: 221

PostPosted: Tue Apr 16, 2019 9:22 am    Post subject: Reply with quote

O.k., so after being a little more careful about when things were happening I did find a fair amount of info in the messages file:

Code:

Apr 16 05:11:38 maya kernel: iwlwifi 0000:03:00.0: Error sending REPLY_ADD_STA: time out after 2000ms.
Apr 16 05:11:38 maya kernel: iwlwifi 0000:03:00.0: Current CMD queue read_ptr 105 write_ptr 109
Apr 16 05:11:38 maya kernel: ------------[ cut here ]------------
Apr 16 05:11:38 maya kernel: Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff)
Apr 16 05:11:38 maya kernel: WARNING: CPU: 3 PID: 8660 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2009 iwl_trans_pcie_grab_nic_access+0x176/0x210 [iwlwifi]
Apr 16 05:11:38 maya kernel: Modules linked in: x86_pkg_temp_thermal iwldvm iwlwifi [last unloaded: vboxdrv]
Apr 16 05:11:38 maya kernel: CPU: 3 PID: 8660 Comm: kworker/u8:1 Tainted: G           O      4.19.27-gentoo-r1 #1
Apr 16 05:11:38 maya kernel: Hardware name: Dell Inc. Latitude E6540/05V0V4, BIOS A05 09/03/2013
Apr 16 05:11:38 maya kernel: Workqueue: phy0 ieee80211_iface_work
Apr 16 05:11:38 maya kernel: RIP: 0010:iwl_trans_pcie_grab_nic_access+0x176/0x210 [iwlwifi]
Apr 16 05:11:38 maya kernel: Code: 8b 7b 30 48 c7 c1 28 78 02 a0 31 d2 31 f6 e8 41 3b ff ff eb 97 89 c6 48 c7 c7 c0 77 02 a0 c6 05 06 2f 02 00 01 e8 9a 67 0d e1 <0f> 0b e9 52 ff ff ff 48 8b 3d 8c 74 56 e2 ba 28 00 00 00 be 20 80
Apr 16 05:11:38 maya kernel: RSP: 0018:ffffc90002477960 EFLAGS: 00010082
Apr 16 05:11:38 maya kernel: RAX: 0000000000000000 RBX: ffff88820f510028 RCX: 0000000000000006
Apr 16 05:11:38 maya kernel: RDX: 0000000000000007 RSI: 0000000000000092 RDI: ffff888216995490
Apr 16 05:11:38 maya kernel: RBP: ffff88820f51a1e8 R08: 0000000000000050 R09: 0000000000000001
Apr 16 05:11:38 maya kernel: R10: ffffc90000cdfde8 R11: 0000000000000001 R12: ffffc90002477988
Apr 16 05:11:38 maya kernel: R13: 00000000ffffffff R14: 0000000000000000 R15: ffff88820f691300
Apr 16 05:11:38 maya kernel: FS:  0000000000000000(0000) GS:ffff888216980000(0000) knlGS:0000000000000000
Apr 16 05:11:38 maya kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 16 05:11:38 maya kernel: CR2: 00001676fa58f028 CR3: 000000000260a005 CR4: 00000000001606e0
Apr 16 05:11:38 maya kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 16 05:11:38 maya kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Apr 16 05:11:38 maya kernel: Call Trace:
Apr 16 05:11:38 maya kernel:  iwl_write_prph+0x32/0x80 [iwlwifi]
Apr 16 05:11:38 maya kernel:  iwl_trans_pcie_send_hcmd+0x367/0x480 [iwlwifi]
Apr 16 05:11:38 maya kernel:  ? wait_woken+0x80/0x80
Apr 16 05:11:38 maya kernel:  iwl_trans_send_cmd+0x59/0xc0 [iwlwifi]
Apr 16 05:11:38 maya kernel:  ? __switch_to_asm+0x40/0x70
Apr 16 05:11:38 maya kernel:  iwl_send_add_sta+0xb0/0x1a0 [iwldvm]
Apr 16 05:11:38 maya kernel:  ? __switch_to_asm+0x34/0x70
Apr 16 05:11:38 maya kernel:  ? __switch_to_asm+0x40/0x70
Apr 16 05:11:38 maya kernel:  ? iwl_sta_rx_agg_stop+0x11c/0x160 [iwldvm]
Apr 16 05:11:38 maya kernel:  iwl_sta_rx_agg_stop+0x11c/0x160 [iwldvm]
Apr 16 05:11:38 maya kernel:  iwlagn_mac_ampdu_action+0x13c/0x1d0 [iwldvm]
Apr 16 05:11:38 maya kernel:  drv_ampdu_action+0x6a/0x140
Apr 16 05:11:38 maya kernel:  ___ieee80211_stop_rx_ba_session+0xcb/0x180
Apr 16 05:11:38 maya kernel:  ieee80211_sta_tear_down_BA_sessions+0x45/0xe0
Apr 16 05:11:38 maya kernel:  __sta_info_destroy_part1+0x40/0x570
Apr 16 05:11:38 maya kernel:  __sta_info_flush+0xc3/0x180
Apr 16 05:11:38 maya kernel:  ieee80211_set_disassoc+0xb2/0x590
Apr 16 05:11:38 maya kernel:  ? iwlagn_mac_tx+0x18/0x30 [iwldvm]
Apr 16 05:11:38 maya kernel:  ieee80211_sta_connection_lost.constprop.27+0x31/0x70
Apr 16 05:11:38 maya kernel:  ieee80211_sta_work+0x24c/0x15b0
Apr 16 05:11:38 maya kernel:  ? __switch_to_asm+0x40/0x70

and a lot more stack trace stuff. None of it is particularly meaningful to me. Later on:
Code:

Apr 16 05:11:38 maya kernel: wlan0: HW problem - can not stop rx aggregation for 48:5d:36:d0:8b:3e tid 0
Apr 16 05:11:40 maya kernel: ieee80211 phy0: Hardware restart was requested
Apr 16 05:11:40 maya kernel: iwlwifi 0000:03:00.0: Fw not loaded - dropping CMD: 18
Apr 16 05:11:40 maya kernel: wlan0: HW problem - can not stop rx aggregation for 48:5d:36:d0:8b:3e tid 1
Apr 16 05:11:40 maya kernel: iwlwifi 0000:03:00.0: Fw not loaded - dropping CMD: 18
Apr 16 05:11:40 maya kernel: wlan0: HW problem - can not stop rx aggregation for 48:5d:36:d0:8b:3e tid 2
Apr 16 05:11:40 maya kernel: iwlwifi 0000:03:00.0: Fw not loaded - dropping CMD: 18
Apr 16 05:11:40 maya kernel: wlan0: HW problem - can not stop rx aggregation for 48:5d:36:d0:8b:3e tid 3
Apr 16 05:11:40 maya kernel: iwlwifi 0000:03:00.0: Fw not loaded - dropping CMD: 18
Apr 16 05:11:40 maya kernel: wlan0: HW problem - can not stop rx aggregation for 48:5d:36:d0:8b:3e tid 4
Apr 16 05:11:40 maya kernel: iwlwifi 0000:03:00.0: Fw not loaded - dropping CMD: 18
Apr 16 05:11:40 maya kernel: wlan0: HW problem - can not stop rx aggregation for 48:5d:36:d0:8b:3e tid 7
Apr 16 05:11:40 maya kernel: WARNING: CPU: 1 PID: 8660 at drivers/net/wireless/intel/iwlwifi/dvm/../iwl-trans.h:1074 iwlagn_mac_flush+0xb2/0xe0 [iwldvm]
Apr 16 05:11:40 maya kernel: Modules linked in: x86_pkg_temp_thermal iwldvm iwlwifi [last unloaded: vboxdrv]
Apr 16 05:11:40 maya kernel: CPU: 1 PID: 8660 Comm: kworker/u8:1 Tainted: G        W  O      4.19.27-gentoo-r1 #1
Apr 16 05:11:40 maya kernel: Hardware name: Dell Inc. Latitude E6540/05V0V4, BIOS A05 09/03/2013
Apr 16 05:11:40 maya kernel: Workqueue: phy0 ieee80211_iface_work
Apr 16 05:11:40 maya kernel: RIP: 0010:iwlagn_mac_flush+0xb2/0xe0 [iwldvm]


etc.

So it looks like the kernel driver is definitely dying. Can anyone make any sense of it? Or even better, any ideas about how I could fix this??

Maybe a very practical question: Since rebooting seems to fix things, how can I reload the modules without doing a full reboot? Just doing rmmod followed by modprobe doesn't seem to be enough. Will using /etc/init.d udev restart reload the device fully?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum