iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

[Christian Vorhauer]

Recently (maybe since updating to linux-image-4.4.0-34-generic:amd64 (4.4.0-34.53), i've not used this notebook to much lately), my wifi connection is unstable, often hangs and therefore spread a lot of bad karma to all networking applications. My log shows entries of the following pattern

Aug 22 20:12:56 nb-voer kernel: [ 1792.518944] iwlwifi 0000:02:00.0: Queue 2 stuck for 10000 ms.
Aug 22 20:12:56 nb-voer kernel: [ 1792.518962] iwlwifi 0000:02:00.0: Current SW read_ptr 86 write_ptr 124
Aug 22 20:12:56 nb-voer kernel: [ 1792.518999] iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Aug 22 20:12:56 nb-voer kernel: [ 1792.519024] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.519037] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x80102065
Aug 22 20:12:56 nb-voer kernel: [ 1792.519050] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.519062] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300001
Aug 22 20:12:56 nb-voer kernel: [ 1792.519075] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.519088] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.519100] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.519113] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x00709052
Aug 22 20:12:56 nb-voer kernel: [ 1792.519163] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [2,2]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519213] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519265] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [86,124]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519326] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519376] iwlwifi 0000:02:00.0: Q 4 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519426] iwlwifi 0000:02:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519476] iwlwifi 0000:02:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519526] iwlwifi 0000:02:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519576] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 3 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519626] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid 0x0000 [83,83]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519676] iwlwifi 0000:02:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519726] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519776] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519826] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519876] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519925] iwlwifi 0000:02:00.0: Q 15 is active and mapped to fifo 5 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519975] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520025] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520075] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520125] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520175] iwlwifi 0000:02:00.0: Q 20 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520225] iwlwifi 0000:02:00.0: Q 21 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520275] iwlwifi 0000:02:00.0: Q 22 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520324] iwlwifi 0000:02:00.0: Q 23 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520374] iwlwifi 0000:02:00.0: Q 24 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520424] iwlwifi 0000:02:00.0: Q 25 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520474] iwlwifi 0000:02:00.0: Q 26 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520524] iwlwifi 0000:02:00.0: Q 27 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520574] iwlwifi 0000:02:00.0: Q 28 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520623] iwlwifi 0000:02:00.0: Q 29 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520674] iwlwifi 0000:02:00.0: Q 30 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520761] iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000.
Aug 22 20:12:56 nb-voer kernel: [ 1792.520763] iwlwifi 0000:02:00.0: CSR values:
Aug 22 20:12:56 nb-voer kernel: [ 1792.520765] iwlwifi 0000:02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Aug 22 20:12:56 nb-voer kernel: [ 1792.520776] iwlwifi 0000:02:00.0: CSR_HW_IF_CONFIG_REG: 0X40489204
Aug 22 20:12:56 nb-voer kernel: [ 1792.520791] iwlwifi 0000:02:00.0: CSR_INT_COALESCING: 0X80000040
Aug 22 20:12:56 nb-voer kernel: [ 1792.520804] iwlwifi 0000:02:00.0: CSR_INT: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520817] iwlwifi 0000:02:00.0: CSR_INT_MASK: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520829] iwlwifi 0000:02:00.0: CSR_FH_INT_STATUS: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520842] iwlwifi 0000:02:00.0: CSR_GPIO_IN: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520855] iwlwifi 0000:02:00.0: CSR_RESET: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520868] iwlwifi 0000:02:00.0: CSR_GP_CNTRL: 0X080403c5
Aug 22 20:12:56 nb-voer kernel: [ 1792.520880] iwlwifi 0000:02:00.0: CSR_HW_REV: 0X00000144
Aug 22 20:12:56 nb-voer kernel: [ 1792.520893] iwlwifi 0000:02:00.0: CSR_EEPROM_REG: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520906] iwlwifi 0000:02:00.0: CSR_EEPROM_GP: 0X80000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520919] iwlwifi 0000:02:00.0: CSR_OTP_GP_REG: 0X803a0000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520931] iwlwifi 0000:02:00.0: CSR_GIO_REG: 0X001f0042
Aug 22 20:12:56 nb-voer kernel: [ 1792.520944] iwlwifi 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520957] iwlwifi 0000:02:00.0: CSR_GP_DRIVER_REG: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520969] iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP1: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520985] iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.520997] iwlwifi 0000:02:00.0: CSR_LED_REG: 0X00000060
Aug 22 20:12:56 nb-voer kernel: [ 1792.521010] iwlwifi 0000:02:00.0: CSR_DRAM_INT_TBL_REG: 0X8803567d
Aug 22 20:12:56 nb-voer kernel: [ 1792.521023] iwlwifi 0000:02:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
Aug 22 20:12:56 nb-voer kernel: [ 1792.521035] iwlwifi 0000:02:00.0: CSR_ANA_PLL_CFG: 0Xd55555d5
Aug 22 20:12:56 nb-voer kernel: [ 1792.521048] iwlwifi 0000:02:00.0: CSR_MONITOR_STATUS_REG: 0X3d0801bd
Aug 22 20:12:56 nb-voer kernel: [ 1792.521061] iwlwifi 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a
Aug 22 20:12:56 nb-voer kernel: [ 1792.521073] iwlwifi 0000:02:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0000
Aug 22 20:12:56 nb-voer kernel: [ 1792.521075] iwlwifi 0000:02:00.0: FH register values:
Aug 22 20:12:56 nb-voer kernel: [ 1792.521097] iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0b3c9d00
Aug 22 20:12:56 nb-voer kernel: [ 1792.521109] iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00b3c9b0
Aug 22 20:12:56 nb-voer kernel: [ 1792.521122] iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_WPTR: 0X000000c0
Aug 22 20:12:56 nb-voer kernel: [ 1792.521134] iwlwifi 0000:02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00801114
Aug 22 20:12:56 nb-voer kernel: [ 1792.521145] iwlwifi 0000:02:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
Aug 22 20:12:56 nb-voer kernel: [ 1792.521157] iwlwifi 0000:02:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X03230000
Aug 22 20:12:56 nb-voer kernel: [ 1792.521169] iwlwifi 0000:02:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.521181] iwlwifi 0000:02:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
Aug 22 20:12:56 nb-voer kernel: [ 1792.521192] iwlwifi 0000:02:00.0: FH_TSSR_TX_ERROR_REG: 0X00000000
Aug 22 20:12:56 nb-voer kernel: [ 1792.521300] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
Aug 22 20:12:56 nb-voer kernel: [ 1792.521302] iwlwifi 0000:02:00.0: Status: 0x00000000, count: 6
Aug 22 20:12:56 nb-voer kernel: [ 1792.521304] iwlwifi 0000:02:00.0: Loaded firmware version: 16.242414.0
Aug 22 20:12:56 nb-voer kernel: [ 1792.521306] iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
Aug 22 20:12:56 nb-voer kernel: [ 1792.521307] iwlwifi 0000:02:00.0: 0x00800634 | uPc
Aug 22 20:12:56 nb-voer kernel: [ 1792.521309] iwlwifi 0000:02:00.0: 0x00000000 | branchlink1
Aug 22 20:12:56 nb-voer kernel: [ 1792.521310] iwlwifi 0000:02:00.0: 0x00000B2C | branchlink2
Aug 22 20:12:56 nb-voer kernel: [ 1792.521312] iwlwifi 0000:02:00.0: 0x00016A90 | interruptlink1
Aug 22 20:12:56 nb-voer kernel: [ 1792.521313] iwlwifi 0000:02:00.0: 0x000095CE | interruptlink2
Aug 22 20:12:56 nb-voer kernel: [ 1792.521315] iwlwifi 0000:02:00.0: 0x00000000 | data1
Aug 22 20:12:56 nb-voer kernel: [ 1792.521316] iwlwifi 0000:02:00.0: 0x00000080 | data2
Aug 22 20:12:56 nb-voer kernel: [ 1792.521318] iwlwifi 0000:02:00.0: 0x07230000 | data3
Aug 22 20:12:56 nb-voer kernel: [ 1792.521319] iwlwifi 0000:02:00.0: 0xFFC2400D | beacon time
Aug 22 20:12:56 nb-voer kernel: [ 1792.521321] iwlwifi 0000:02:00.0: 0x6AFA2FF2 | tsf low
Aug 22 20:12:56 nb-voer kernel: [ 1792.521322] iwlwifi 0000:02:00.0: 0x00000009 | tsf hi
Aug 22 20:12:56 nb-voer kernel: [ 1792.521324] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
Aug 22 20:12:56 nb-voer kernel: [ 1792.521325] iwlwifi 0000:02:00.0: 0x00BE0EA7 | time gp2
Aug 22 20:12:56 nb-voer kernel: [ 1792.521327] iwlwifi 0000:02:00.0: 0x00000000 | time gp3
Aug 22 20:12:56 nb-voer kernel: [ 1792.521328] iwlwifi 0000:02:00.0: 0x00000010 | uCode version major
Aug 22 20:12:56 nb-voer kernel: [ 1792.521330] iwlwifi 0000:02:00.0: 0x0003B2EE | uCode version minor
Aug 22 20:12:56 nb-voer kernel: [ 1792.521331] iwlwifi 0000:02:00.0: 0x00000144 | hw version
Aug 22 20:12:56 nb-voer kernel: [ 1792.521333] iwlwifi 0000:02:00.0: 0x40489204 | board version
Aug 22 20:12:56 nb-voer kernel: [ 1792.521334] iwlwifi 0000:02:00.0: 0x0256001C | hcmd
Aug 22 20:12:56 nb-voer kernel: [ 1792.521336] iwlwifi 0000:02:00.0: 0xA4022002 | isr0
Aug 22 20:12:56 nb-voer kernel: [ 1792.521337] iwlwifi 0000:02:00.0: 0x01000000 | isr1
Aug 22 20:12:56 nb-voer kernel: [ 1792.521339] iwlwifi 0000:02:00.0: 0x0000000A | isr2
Aug 22 20:12:56 nb-voer kernel: [ 1792.521340] iwlwifi 0000:02:00.0: 0x004078C4 | isr3
Aug 22 20:12:56 nb-voer kernel: [ 1792.521342] iwlwifi 0000:02:00.0: 0x00000000 | isr4
Aug 22 20:12:56 nb-voer kernel: [ 1792.521343] iwlwifi 0000:02:00.0: 0x00004110 | isr_pref
Aug 22 20:12:56 nb-voer kernel: [ 1792.521346] iwlwifi 0000:02:00.0: 0x00000000 | wait_event
Aug 22 20:12:56 nb-voer kernel: [ 1792.521347] iwlwifi 0000:02:00.0: 0x00000080 | l2p_control
Aug 22 20:12:56 nb-voer kernel: [ 1792.521349] iwlwifi 0000:02:00.0: 0x00012030 | l2p_duration
Aug 22 20:12:56 nb-voer kernel: [ 1792.521350] iwlwifi 0000:02:00.0: 0x0000003F | l2p_mhvalid
Aug 22 20:12:56 nb-voer kernel: [ 1792.521352] iwlwifi 0000:02:00.0: 0x000000CE | l2p_addr_match
Aug 22 20:12:56 nb-voer kernel: [ 1792.521353] iwlwifi 0000:02:00.0: 0x00000005 | lmpm_pmg_sel
Aug 22 20:12:56 nb-voer kernel: [ 1792.521355] iwlwifi 0000:02:00.0: 0x17111905 | timestamp
Aug 22 20:12:56 nb-voer kernel: [ 1792.521356] iwlwifi 0000:02:00.0: 0x0034C0D0 | flow_handler
Aug 22 20:12:56 nb-voer kernel: [ 1792.521360] ieee80211 phy0: Hardware restart was requested
Aug 22 20:12:56 nb-voer kernel: [ 1792.658776] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
Aug 22 20:12:56 nb-voer kernel: [ 1792.659531] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
Aug 22 20:12:57 nb-voer kernel: [ 1792.876865] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
Aug 22 20:12:57 nb-voer kernel: [ 1792.877528] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-34-generic 4.4.0-34.53
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: voer 4238 F.... pulseaudio
 /dev/snd/controlC0: voer 4238 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Aug 22 20:24:32 2016
HibernationDevice: RESUME=UUID=55e6a4cb-99d0-4a44-a638-b9cd2e797ba0
InstallationDate: Installed on 2015-12-12 (254 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Hewlett-Packard HP EliteBook 840 G1
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-34-generic N/A
 linux-backports-modules-4.4.0-34-generic N/A
 linux-firmware 1.157.3
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-05-18 (95 days ago)
dmi.bios.date: 12/09/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.30
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.55
dmi.chassis.asset.tag: 5CG5073W9Z
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.30:bd12/09/2014:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.55:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 840 G1
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3

[Brad Figg (brad-figg)]

This change was made by a bot.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[noob saibot (odmartin)]

Bios update helped in my case. I had this problem every 5-15 min. First got "Queue stuck" then "Microcode SW error detected" I have the same firmware

Loaded firmware version: 16.242414.0

as the OP but a slightly newer kernel:

uname -r
4.4.0-59-generic

I have a Lenovo Yoga 260 and Network controller: Intel Corporation Wireless 8260 (rev 3a).

[noob saibot (odmartin)]

Nope, I celebrated too early. I still get this error with the updated bios. Apparently less frequently.

[penalvch (penalvch)]

noob saibot, it will help immensely if you filed a new report with Ubuntu, using the default repository kernel (not mainline/upstream/3rd party) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Radek Dostal (radekdostal)]

Just for information: my girlfriend seem to have the same issue. Updating her Lenovo IdeaPad U430 to kernel 4.8 (HWE stack from 16.04.2) did NOT help.

On the other hand, reconfiguring Wi-Fi from 40MHz to 20MHz as described at https://<email address hidden>/msg10469.html did solve the issue!

[Heinz Werner (heinzken)]

Hello altogether, I am affected too. From time to time the same error occurs, showing the "queue stuck" and "Hardware restart" messages, while WiFi-connection is not working. It happens then in a loop. I am not running Ubuntu, I am running aptosid with "4.10.0-8.slh.1-aptosid-amd64 #1 SMP PREEMPT aptosid 4.10-13 (2017-04-06) x86_64 GNU/Linux". So this could be a *linux-generic* problem:

Excerpt of messages-entries:

 Apr 29 11:23:18 MyNiceNode kernel: iwlwifi 0000:02:00.0: Queue 4 stuck for 10000 ms.
 Apr 29 11:23:18 MyNiceNode kernel: iwlwifi 0000:02:00.0: Current SW read_ptr 234 write_ptr 15
 Apr 29 11:23:18 MyNiceNode kernel: iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 Apr 29 11:23:18 MyNiceNode kernel: iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
 Apr 29 11:23:18 MyNiceNode kernel: iwlwifi 0000:02:00.0: FH TRBs(1) = 0xc01040f9
 Apr 29 11:23:18 MyNiceNode kernel: iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
 ...
 Apr 29 11:23:18 MyNiceNode kernel: iwlwifi 0000:02:00.0: 0x00000007 | lmpm_pmg_sel
 Apr 29 11:23:18 MyNiceNode kernel: iwlwifi 0000:02:00.0: 0x03071928 | timestamp
 Apr 29 11:23:18 MyNiceNode kernel: iwlwifi 0000:02:00.0: 0x003490A0 | flow_handler
 Apr 29 11:23:18 MyNiceNode kernel: ieee80211 phy8: Hardware restart was requested
 Apr 29 11:23:18 MyNiceNode kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
 Apr 29 11:23:18 MyNiceNode kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled

I have this issue since several releases, but I don't remember exactly, when it started.

***
But today I got aware, of how to "fix" it... I was running a USB3-connected harddisk,
and when I disconnect it, problems immediately gone!!!
***

Stalled downloads continue, WiFi is working flawless again, as soon the drive is gone.

And as soon I connect USB3-HDD again (just connect, you even don't have to mount a filesystem, the WLAN-error-loop gets me again!

So I see a connection toe USB3-hardware-internals? Maybe a hardware-problem, triggered somehow, or something with USB-stack... but I don't understand, how it can influence WiFi.

I am running Linux on a Dell Latitude E7450. I have some kernel-parameters in use, maybe they have influence too, so for your information:

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.10.0-8.slh.1-aptosid-amd64 root=/dev/mapper/MyNiceNode-lroot ro i8042.nopnp atkbd.reset pcie_aspm=force nmi_watchdog=0 libata.force=noncq video=SVIDEO-1:d

The WiFi-card is a:

$ lspci|grep -i wire
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)

And in more detail with lshw-excerpt:

        *-pci:1
             description: PCI bridge
             product: Wildcat Point-LP PCI Express Root Port #4
             vendor: Intel Corporation
             physical id: 1c.3
             bus info: pci@0000:00:1c.3
             version: e3
             width: 32 bits
             clock: 33MHz
             capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
             configuration: driver=pcieport
             resources: irq:43 ioport:3000(size=4096) memor...

[Kai-Heng Feng (kaihengfeng)]

See if removing "pcie_aspm=force" helps.

Why do you need "i8042.nopnp" and "atkbd.reset"? Most Dell laptop should work out of the box, those kernel parameters are not required.

[Heinz Werner (heinzken)]

Thank you for the tip, Kai-Heng Feng, I will observere what happens, when I remove "pcie_aspm=force".

I added it long time ago, Apr 2014. Reason was, that my notebook then, a Dell M2400, sometimes didn't survive resume after standby (1 of 10 times maybe). It just crashed, black screen, X11 dead. The option didn't really help that days, but it survived my config somehow ;-)

However, even today with Dell E7450 I sometimes have weird situations, where system is gone that way without any "visible" cause. Last time in April with 4.10.0-8.slh.1-aptosid-amd64 (I am now on 4.11.0-0.slh.1-aptosid-amd64), in the middle of using it, doing "nothing special".

I must say, that I am using the notebook in a very "dynamic" way, that may be unusual to others:
(*) I use it constantly using standby/resume, when I don't need it
(*) Rebooting only on dist-upgrades, kernel-upgrades or some backups
(*) Constantly plug/unplugging HW to notebook (USB-Devices, Dockingstation, ext. Monitors)

I had issues, where it didn't seem to be good, to have system in a docking station, then send it to standby, remove it from dock, and resume system. I guess, that shouldn't make any difference but I try to avoid that, after some crashes .

Since my last post, I didn't experience the vanishing WLAN again.

Situation didn't get better overall with USB3-Devices (I miss eSata-ports).
I cannot use double-bay-USB3-Adapters. Rsyncing two discs leads to Disconnects
sooner or later under heavy load.
Or accessing a USB2-CD/DVD and having in parallel I/O to a USB3-connected HDD,
I repeatedly had the situation of USB3-HDD disconnecting.
When I reconnect, and havingsame workload again, no problem for hours.

And seeing USB3 having influence on your WLAN is weird :-)

But I am just guessing. I will remove unnecessary kernel-parameter first
and then observe.
Thank you for helping!

[Kai-Heng Feng (kaihengfeng)]

Please file a new bug for USB-HDD issue. Probably needs to quirk off the device to make it work.

[Heinz Werner (heinzken)]

Just stumbled over an article in ct 12/2017 Page 162 (german computer magazin). It says, USB3 can intereference with devices like 2.4Ghz WLAN, USB-receivers.

References:
White-Paper Intel: http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb3-frequency-interference-paper.html
Asus-FAQ: https://www.asus.com/de/support/faq/1004004/

So maybe the wohle thing is "hardware"-related and no SW-issue...
Furthermore, I didn't have the error for a long time now.
When I experienced it, I had external USB3-drive with a short cable connected. It seems to be depending further on the exact hardware, the cable it's using and the position of the devices involved.

Get the tinfoil ;-)

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]