You are not logged in.
Pages: 1
Topic closed
I have a Dell XPS 13 9343 (early 2015) that has been giving me Wifi problems for a while (also some audio problems, but I'm assuming that's unrelated and I can live with it).
What's happening is that my wifi acts completely normal, it stays connected by all indications but nothing gets through. Not even a ping. When that happens I just run
sudo systemctl restart NetworkManager
and it will typically stay connected again for a while. The weird thing is that I can go a long time without seeing this issue, especially on my home network, but when I go out to coffee shops and other places, it seems to happen pretty often. Sometimes so often that it's really unusable.
I haven't been able to figure out what exactly is going on to trigger this. The best indication that something is wrong seems to be this entry that I find in the logs from time to time
Queue 2 stuck for 10000 ms
then
Microcode SW error detected. Restarting
But it doesn't seem to directly coincide to when my Wifi dies. I'll include the full error from the logs below.
I've tried miscellaneous things like using linux-firmware-iwlwifi-git and disabling power saving mode or 11n, and nothing seems to help. My next step is going to be reinstalling Arch, but I'm not looking forward to that since I use this laptop for work and I'm sure it would take me a while to get everything set up again.
Any help is appreciated. Thanks.
From iwconfig:
wlp2s0 IEEE 802.11 ESSID:"PLDTHOMEFIBRFORCEDADVERTISING"
Mode:Managed Frequency:2.457 GHz Access Point: D0:04:92:00:18:30
Bit Rate=104 Mb/s Tx-Power=22 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=42/70 Signal level=-68 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:192 Missed beacon:0
From dmesg:
[ 349.068268] iwlwifi 0000:02:00.0: Queue 2 stuck for 10000 ms.
[ 349.068274] iwlwifi 0000:02:00.0: Current SW read_ptr 135 write_ptr 195
[ 349.068318] iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 349.068342] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[ 349.068363] iwlwifi 0000:02:00.0: FH TRBs(1) = 0xc01100f7
[ 349.068375] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[ 349.068397] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x8030000d
[ 349.068409] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[ 349.068422] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[ 349.068443] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[ 349.068465] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090b7
[ 349.068526] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [14,14]
[ 349.068597] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [0,0]
[ 349.068647] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [135,195]
[ 349.068697] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.068747] iwlwifi 0000:02:00.0: Q 4 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.068796] iwlwifi 0000:02:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.068847] iwlwifi 0000:02:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.068904] iwlwifi 0000:02:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.068953] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 3 ra_tid 0x0000 [0,0]
[ 349.069010] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid 0x0000 [184,184]
[ 349.069060] iwlwifi 0000:02:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069110] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069159] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069209] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069259] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069309] iwlwifi 0000:02:00.0: Q 15 is active and mapped to fifo 5 ra_tid 0x0000 [0,0]
[ 349.069382] iwlwifi 0000:02:00.0: Q 16 is active and mapped to fifo 1 ra_tid 0x0000 [232,38]
[ 349.069433] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069489] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069549] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069600] iwlwifi 0000:02:00.0: Q 20 is inactive and mapped to fifo 0 ra_tid 0xff00 [0,0]
[ 349.069649] iwlwifi 0000:02:00.0: Q 21 is inactive and mapped to fifo 0 ra_tid 0x00ff [0,0]
[ 349.069698] iwlwifi 0000:02:00.0: Q 22 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069747] iwlwifi 0000:02:00.0: Q 23 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069796] iwlwifi 0000:02:00.0: Q 24 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069844] iwlwifi 0000:02:00.0: Q 25 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069902] iwlwifi 0000:02:00.0: Q 26 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.069950] iwlwifi 0000:02:00.0: Q 27 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.070000] iwlwifi 0000:02:00.0: Q 28 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.070057] iwlwifi 0000:02:00.0: Q 29 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.070114] iwlwifi 0000:02:00.0: Q 30 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 349.070189] iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 349.070192] iwlwifi 0000:02:00.0: CSR values:
[ 349.070194] iwlwifi 0000:02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
[ 349.070211] iwlwifi 0000:02:00.0: CSR_HW_IF_CONFIG_REG: 0X00489200
[ 349.070249] iwlwifi 0000:02:00.0: CSR_INT_COALESCING: 0X00000040
[ 349.070272] iwlwifi 0000:02:00.0: CSR_INT: 0X00000000
[ 349.070286] iwlwifi 0000:02:00.0: CSR_INT_MASK: 0X00000000
[ 349.070301] iwlwifi 0000:02:00.0: CSR_FH_INT_STATUS: 0X00000000
[ 349.070316] iwlwifi 0000:02:00.0: CSR_GPIO_IN: 0X00000000
[ 349.070327] iwlwifi 0000:02:00.0: CSR_RESET: 0X00000000
[ 349.070339] iwlwifi 0000:02:00.0: CSR_GP_CNTRL: 0X080403c5
[ 349.070376] iwlwifi 0000:02:00.0: CSR_HW_REV: 0X00000210
[ 349.070398] iwlwifi 0000:02:00.0: CSR_EEPROM_REG: 0Xd55555d5
[ 349.070420] iwlwifi 0000:02:00.0: CSR_EEPROM_GP: 0X00000000
[ 349.070436] iwlwifi 0000:02:00.0: CSR_OTP_GP_REG: 0Xd55555d5
[ 349.070451] iwlwifi 0000:02:00.0: CSR_GIO_REG: 0X001f0042
[ 349.070463] iwlwifi 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000000
[ 349.070479] iwlwifi 0000:02:00.0: CSR_GP_DRIVER_REG: 0X00000000
[ 349.070495] iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP1: 0X00000000
[ 349.070510] iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000
[ 349.070521] iwlwifi 0000:02:00.0: CSR_LED_REG: 0X00000060
[ 349.070533] iwlwifi 0000:02:00.0: CSR_DRAM_INT_TBL_REG: 0X88213db8
[ 349.070545] iwlwifi 0000:02:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
[ 349.070558] iwlwifi 0000:02:00.0: CSR_ANA_PLL_CFG: 0Xd55555d5
[ 349.070573] iwlwifi 0000:02:00.0: CSR_MONITOR_STATUS_REG: 0Xc3b7ff77
[ 349.070587] iwlwifi 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a
[ 349.070599] iwlwifi 0000:02:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0010
[ 349.070600] iwlwifi 0000:02:00.0: FH register values:
[ 349.070622] iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X21409a00
[ 349.070635] iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X021409b0
[ 349.070646] iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_WPTR: 0X000000d8
[ 349.070658] iwlwifi 0000:02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00801114
[ 349.070669] iwlwifi 0000:02:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
[ 349.070680] iwlwifi 0000:02:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X03030000
[ 349.070694] iwlwifi 0000:02:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
[ 349.070713] iwlwifi 0000:02:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
[ 349.070733] iwlwifi 0000:02:00.0: FH_TSSR_TX_ERROR_REG: 0X00000000
[ 349.070858] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[ 349.070859] iwlwifi 0000:02:00.0: Status: 0x00000000, count: 6
[ 349.070861] iwlwifi 0000:02:00.0: Loaded firmware version: 22.391740.0
[ 349.070863] iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
[ 349.070864] iwlwifi 0000:02:00.0: 0x00A00230 | trm_hw_status0
[ 349.070865] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
[ 349.070866] iwlwifi 0000:02:00.0: 0x00043850 | branchlink2
[ 349.070867] iwlwifi 0000:02:00.0: 0x0004A5E8 | interruptlink1
[ 349.070868] iwlwifi 0000:02:00.0: 0x0004A5E8 | interruptlink2
[ 349.070869] iwlwifi 0000:02:00.0: 0x00000000 | data1
[ 349.070870] iwlwifi 0000:02:00.0: 0x00000080 | data2
[ 349.070872] iwlwifi 0000:02:00.0: 0x07030000 | data3
[ 349.070873] iwlwifi 0000:02:00.0: 0x73C0585C | beacon time
[ 349.070874] iwlwifi 0000:02:00.0: 0xBA3BB79B | tsf low
[ 349.070875] iwlwifi 0000:02:00.0: 0x0000003A | tsf hi
[ 349.070876] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[ 349.070877] iwlwifi 0000:02:00.0: 0x0326E98C | time gp2
[ 349.070878] iwlwifi 0000:02:00.0: 0x00000000 | uCode revision type
[ 349.070879] iwlwifi 0000:02:00.0: 0x00000016 | uCode version major
[ 349.070880] iwlwifi 0000:02:00.0: 0x0005FA3C | uCode version minor
[ 349.070881] iwlwifi 0000:02:00.0: 0x00000210 | hw version
[ 349.070882] iwlwifi 0000:02:00.0: 0x00489200 | board version
[ 349.070883] iwlwifi 0000:02:00.0: 0x10E8001C | hcmd
[ 349.070884] iwlwifi 0000:02:00.0: 0x24022002 | isr0
[ 349.070885] iwlwifi 0000:02:00.0: 0x00800000 | isr1
[ 349.070886] iwlwifi 0000:02:00.0: 0x00000002 | isr2
[ 349.070887] iwlwifi 0000:02:00.0: 0x004174C0 | isr3
[ 349.070888] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[ 349.070889] iwlwifi 0000:02:00.0: 0x00000110 | last cmd Id
[ 349.070890] iwlwifi 0000:02:00.0: 0x00000000 | wait_event
[ 349.070891] iwlwifi 0000:02:00.0: 0x00000080 | l2p_control
[ 349.070892] iwlwifi 0000:02:00.0: 0x00010030 | l2p_duration
[ 349.070893] iwlwifi 0000:02:00.0: 0x0000003F | l2p_mhvalid
[ 349.070894] iwlwifi 0000:02:00.0: 0x00000080 | l2p_addr_match
[ 349.070895] iwlwifi 0000:02:00.0: 0x00000015 | lmpm_pmg_sel
[ 349.070896] iwlwifi 0000:02:00.0: 0x25091923 | timestamp
[ 349.070897] iwlwifi 0000:02:00.0: 0x0034D8E8 | flow_handler
Offline
As a sanity check, what is the output of find /etc/systemd?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Here's what I get
find /etc/systemd
/etc/systemd
/etc/systemd/journal-remote.conf
/etc/systemd/user
/etc/systemd/user/sockets.target.wants
/etc/systemd/user/sockets.target.wants/pulseaudio.socket
/etc/systemd/user/default.target.wants
/etc/systemd/user/default.target.wants/xdg-user-dirs-update.service
/etc/systemd/logind.conf
/etc/systemd/resolved.conf
/etc/systemd/network
/etc/systemd/journal-upload.conf
/etc/systemd/timesyncd.conf
/etc/systemd/system
/etc/systemd/system/sysinit.target.wants
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/systemd/system/dbus-org.bluez.service
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/dhcpcd.service
/etc/systemd/system/multi-user.target.wants/sshd.service
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/multi-user.target.wants/dnsmasq.service
/etc/systemd/system/multi-user.target.wants/org.cups.cupsd.path
/etc/systemd/system/bluetooth.target.wants
/etc/systemd/system/bluetooth.target.wants/bluetooth.service
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
/etc/systemd/system/printer.target.wants
/etc/systemd/system/printer.target.wants/org.cups.cupsd.service
/etc/systemd/system/sockets.target.wants
/etc/systemd/system/sockets.target.wants/org.cups.cupsd.socket
/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service
/etc/systemd/system/display-manager.service
/etc/systemd/system.conf
/etc/systemd/coredump.conf
/etc/systemd/journald.conf
/etc/systemd/user.conf
Offline
Disable your dhcpcd service. Network manager uses the dhcpcd daemon directly and controls it as needed. The systemd dhcpcd service also controls the dhcpcd daemon, but it ways that conflict with NetworkManager.
I also think you need to disable network, that is part of systemd-network that also conflicts (I think)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Thanks! I ran the commands below and restarted for good measure.
network.target seems to still be loaded by something, but dhcpcd isn't, so that's good. I'll check back in later with the results since it generally happens sporadically.
➜ ~ sudo systemctl stop dhcpcd.service
➜ ~ sudo systemctl stop network.target
➜ ~ sudo systemctl disable dhcpcd.service
Removed /etc/systemd/system/multi-user.target.wants/dhcpcd.service.
➜ ~ sudo systemctl disable network.target
Offline
Seems like it's still happening. I saw the same Microcode error in the logs this morning and am seeing the same dead wifi issue.
I can kill the network.target unit but restarting NetworkManager seems to fire it back up again.
Offline
...
I can kill the network.target unit but restarting NetworkManager seems to fire it back up again.
Killing network.target is not needed. It does not conflict with your networkmanager.service, actually your networkmanager.service file shall have "Wants=network.target" line.
For more details about this https://www.freedesktop.org/wiki/Softwa … orkTarget/
Also read this for microcode related error
https://wiki.archlinux.org/index.php/Microcode
Arch is home!
https://github.com/Docbroke
Offline
Thanks Docbroke, I figured network.target was tied to some other service.
I think I've been through all the microcode steps recently. I'm currently running the latest iwlwifi firmware with linux-firmware-iwlwifi-git. But it hasn't seemed to change anything.
I've confirmed that the microcode is being updated in dmesg:
microcode updated early to revision 0x24, date = 2016-04-29
Offline
Are you disabling power saving mode with
sudo iwconfig wlp2s0 power off
Or are you trying to do it through iwlwifi parameters?
Offline
I don't remember exactly what I did now. It was a while ago. I believe I changed it in a config file somewhere. I'll try
sudo iwconfig wlp2s0 power off
and see how it goes. Thanks.
Offline
Just took my laptop out to a coffee shop and I had the same issues as always, unfortunately.
I haven't seen the "Microcode SW error detected" error in a while, so that's a good sign. But I suppose that means that error is unrelated to the issues I've been happening.
Offline
Was your problem solved? Currently, I'm having the same issues...
Offline
Anubhav, please do not necrobump old threads. If you are still having the same problem, feel free to start your own thread and describe the problem with logs and errors, as well as what you have tried to do to solve it.
Offline
Anubhav,
Please open a new thread on the topic. This issue is probably not the same as the one from this thread -- much water has gone under the bridge since this thread was created.
Thanks
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Pages: 1
Topic closed