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) memory:f7100000-f71fffff
ioport:cfa00000(size=2097152)
*-network
description: Wireless interface
product: Wireless 7265
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0
version: 59
serial: a4:02:b9:0f:1c:5c
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet
physical wireless
configuration: broadcast=yes driver=iwlwifi
driverversion=4.10.0-8.slh.1-aptosid-amd64 firmware=22.361476.0 ip=192.168.0.7
latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:52 memory:f7100000-f7101fff
The USB3-HDD is directly connected to a USB-interface at the back of the
laptop, via a IcyBox IB-AC703-U3 interface.
When I run (the same) HDDs within a HardiskDock connected via esata, I don't
have WiFi-restarts either (Latitude E7450 sadly lacks direct esata-ports, so I
have a DockingStation to make use of esata).
Maybe someone can confirm having connected some USB stuff to the systems, when
the problems pop up?
And (maybe) not directly connected to this issue, but I experienced more
weird USB(3)-related phenomens, I may describe later, but all resulting
in bus-resets so devices are "gone". I miss my esata, that was stable
with multiple-disk-IO.
However, I hope, I can help with my input!
Regards
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615774
Title:
iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0:
Hardware restart was requested
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615774/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
