[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Brad Figg]

** Tags added: cscc

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Gold Star]

I have the same issue with Linux Mint 19 (Ubuntu 18.04 based) using
kernel 4.15 but for QCA9377 chipset.

I compiled the 4.18 kernel using `make localmodconfig` and have the same 
problem. 
I had sources for kernel version 4.9.24 and it exhibits the same behavior 
(failed to wake target for write32) after going to suspend and then turning 
back on.

Computer is a Dell Inspiron 14 3473.

I've tried numerous debug steps like restarting network-manager,
removing mac80211 cfg80211 ath10k ath10k_core and ath10k_pci modules
then reinserting them and then restarting network-manager with no
improvement.

I have not played with "Wake on Wireless" settings yet
(https://wireless.wiki.kernel.org/en/users/documentation/wowlan)

While I have the QCA9377 I do believe this post is quite relavant:
https://patchwork.kernel.org/patch/7548331/ so I'm going to check if
that patch works for the QCA9377 and report back.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Dmitrii Shcherbakov]

Gathering more evidence in support of a faulty motherboard theory.

At some point I got this (system wasn't under heavy load - just a
browser opened + remote video playback):

https://gist.github.com/dshcherb/06f4e4a0260b6d5313df1594d959849a#file-
nvme-failure-razer-dmesg-log-L2073


сен 10 22:23:39 blade kernel: nvme nvme0: I/O 916 QID 3 timeout, aborting
сен 10 22:23:39 blade kernel: nvme nvme0: I/O 917 QID 3 timeout, aborting
сен 10 22:23:39 blade kernel: nvme nvme0: I/O 918 QID 3 timeout, aborting
сен 10 22:23:39 blade kernel: nvme nvme0: I/O 919 QID 3 timeout, aborting
сен 10 22:23:45 blade kernel: nvme nvme0: I/O 920 QID 3 timeout, aborting
сен 10 22:23:55 blade kernel: nvme nvme0: I/O 921 QID 3 timeout, aborting
сен 10 22:24:10 blade kernel: nvme nvme0: I/O 916 QID 3 timeout, reset 
controller
сен 10 22:24:39 blade kernel: nvme nvme0: I/O 11 QID 0 timeout, reset controller
сен 10 22:25:42 blade kernel: nvme nvme0: Device not ready; aborting reset

So the kernel tried to reset a controller after a timeout which is
normal and could not do so after 100ms => aborted reset.

http://elixir.free-
electrons.com/linux/v4.13/source/drivers/nvme/host/core.c#L1378

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Dmitrii Shcherbakov]

Sorry, I should have mentioned that before: in the original test I also
had a device plugged in via usb type-c (thunderbolt 3) - that device had
an ethernet interface which you can see in the logs. It's another
problem that I need to debug because type-c hot-plug of that device
worked once but successive attempts did not (no devices were attached) -
will try that on 4.13 but not in the scope of this thread.

I think we can safely ignore ax88179_178a for now:

мар 07 17:23:47 blade kernel: ax88179_178a 4-1.1:1.0 eth0: register
'ax88179_178a' at usb-:10:00.0-1.1, ASIX AX88179 USB 3.0 Gigabit
Ethernet, 00:05:6b:00:6a:d7

Regarding hid-rmi - I have not encountered visible problems with a
touchpad or keyboard after restore (or have not noticed them).

The original log messages were on suspend:

[18433.618894] PM: Suspending system (mem)
[18433.618956] Suspending console(s) (use no_console_suspend to debug)
[18434.736072] hid-rmi 0018:06CB:5F41.0005: rmi_read_block: timeout elapsed
[18435.760072] hid-rmi 0018:06CB:5F41.0005: rmi_read_block: timeout elapsed
[18436.784071] hid-rmi 0018:06CB:5F41.0005: rmi_read_block: timeout elapsed
[18437.808071] hid-rmi 0018:06CB:5F41.0005: rmi_read_block: timeout elapsed
[18438.832072] hid-rmi 0018:06CB:5F41.0005: rmi_read_block: timeout elapsed
[18438.832076] hid-rmi 0018:06CB:5F41.0005: can not read F11 control registers
[18439.041909] pcieport :03:02.0: Refused to change power state, currently 
in D3
[18439.041917] pcieport :03:00.0: Refused to change power state, currently 
in D3
[18439.168298] ACPI : EC: event blocked
[18439.377161] PM: suspend of devices complete after 5653.226 msecs
[18439.399735] PM: late suspend of devices complete after 22.568 msecs

After systemctl suspend and resume on 4.13:

http://paste.ubuntu.com/25505431/
http://paste.ubuntu.com/25505433/ (full dmesg)
[132638.096488] PM: Suspending system (mem)
[132638.096517] Suspending console(s) (use no_console_suspend to debug)
[132639.666295] PM: suspend of devices complete after 1356.062 msecs
[132639.689669] PM: late suspend of devices complete after 23.366 msecs
[132639.774466] PM: noirq suspend of devices complete after 84.791 msecs
...

---

So, I think both of those may be ignored for now.

** Attachment added: "type-c-device-razer-core.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+attachment/4947391/+files/type-c-device-razer-core.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Kai-Heng Feng]

You mean both ax88179_178a and hid-rmi work?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Dmitrii Shcherbakov]

I will try 2 things:

1. re-seat the card

2. get a card from a different manufacturer and test.

It might be a buggy slot in the motherboard and if the problem persists
with a new card I will know for sure that the slot is defective.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Dmitrii Shcherbakov]

This is the most heavily loaded configuration I use with this device and
I don't have issues with either an NVMe SSD or GPU. No hardware-related
issues with any USB devices (data goes through PCIe in the end).

➜  ~ lspci -v -t 
-[:00]-+-00.0  Intel Corporation Device 5910
   +-01.0-[01]00.0  NVIDIA Corporation GP106M [GeForce GTX 1060 
Mobile]
   +-02.0  Intel Corporation Device 591b
   +-14.0  Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller
   +-14.2  Intel Corporation Sunrise Point-H Thermal subsystem
   +-15.0  Intel Corporation Sunrise Point-H Serial IO I2C Controller #0
   +-16.0  Intel Corporation Sunrise Point-H CSME HECI #1
   +-1c.0-[02-3a]00.0-[03-06]--+-00.0-[04]--
   |   +-01.0-[05]--
   |   \-02.0-[06]00.0  Intel 
Corporation Device 15db
   +-1c.5-[3b]00.0  Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter
   +-1d.0-[3c]00.0  Samsung Electronics Co Ltd NVMe SSD Controller 
SM961/PM961
   +-1e.0  Intel Corporation Sunrise Point-H Serial IO UART #0
   +-1f.0  Intel Corporation Sunrise Point-H LPC Controller
   +-1f.2  Intel Corporation Sunrise Point-H PMC
   +-1f.3  Intel Corporation Device a171
   \-1f.4  Intel Corporation Sunrise Point-H SMBus

➜  ~ lsusb -v -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
|__ Port 5: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 5: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 13, If 2, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 1: Dev 13, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 1: Dev 13, If 3, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 1: Dev 13, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 2: Dev 7, If 0, Class=Hub, Driver=hub/4p, 12M
|__ Port 3: Dev 10, If 1, Class=Human Interface Device, 
Driver=usbhid, 12M
|__ Port 3: Dev 10, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
|__ Port 1: Dev 8, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
|__ Port 1: Dev 8, If 1, Class=Human Interface Device, 
Driver=usbhid, 1.5M
|__ Port 4: Dev 11, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
|__ Port 2: Dev 47, If 2, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 2: Dev 47, If 0, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 2: Dev 47, If 3, Class=Human Interface Device, 
Driver=usbhid, 12M
|__ Port 2: Dev 47, If 1, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 7: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 7: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 8: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 8: Dev 6, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 8: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M

Maybe I should swap this card out for something else like Intel 8260 or
an upcoming 9260 to test out whether this is a PCIe issue but I don't
think it is.

Found this unanswered thread at infradead with the exact same hardware but a 
different PCIe setup:
http://lists.infradead.org/pipermail/ath10k/2017-June/009904.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Dmitrii Shcherbakov]

I did get a lot of corrected PCIe errors previously which is why I set 
pcie_aspm=off (otherwise it flooded my kernel log instantly) 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687714
https://launchpadlibrarian.net/318000853/dmesg_pcie_aspm_rc8.log

I need to think of a good test for other devices but I have not noticed
any obvious failures yet.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Kai-Heng Feng]

Seems like it's a PCI bus issue? Tons of errors happened before the
ath10k_pci errors:

мар 07 01:54:20 hostname kernel: ax88179_178a 4-1.1:1.0 enx00056b006ad7: Failed 
to read reg index 0x0002: -19
мар 07 01:54:20 hostname kernel: ax88179_178a 4-1.1:1.0 enx00056b006ad7: Failed 
to write reg index 0x0002: -19
мар 07 01:54:21 hostname kernel: ax88179_178a 4-1.1:1.0 enx00056b006ad7 
(unregistered): Failed to write reg index 0x0002: -19
мар 07 01:54:21 hostname kernel: ax88179_178a 4-1.1:1.0 enx00056b006ad7 
(unregistered): Failed to write reg index 0x0001: -19
мар 07 01:54:21 hostname kernel: ax88179_178a 4-1.1:1.0 enx00056b006ad7 
(unregistered): Failed to write reg index 0x0002: -19
мар 07 01:54:21 hostname kernel: xhci_hcd :08:00.0: Host halt failed, -19
мар 07 01:54:21 hostname kernel: xhci_hcd :08:00.0: Host not accessible, 
reset failed.
..
мар 07 15:10:56 hostname kernel: hid-rmi 0018:06CB:5F41.0005: rmi_read_block: 
timeout elapsed
мар 07 15:10:56 hostname kernel: hid-rmi 0018:06CB:5F41.0005: rmi_read_block: 
timeout elapsed
мар 07 15:10:56 hostname kernel: hid-rmi 0018:06CB:5F41.0005: rmi_read_block: 
timeout elapsed
мар 07 15:10:56 hostname kernel: hid-rmi 0018:06CB:5F41.0005: rmi_read_block: 
timeout elapsed
мар 07 15:10:56 hostname kernel: hid-rmi 0018:06CB:5F41.0005: rmi_read_block: 
timeout elapsed
мар 07 15:10:56 hostname kernel: hid-rmi 0018:06CB:5F41.0005: can not read F11 
control registers

So the question here is, do other devices also fail to work?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Dmitrii Shcherbakov]

I don't have a special wireless off/on button on my keyboard but I'm
assuming rfkill   will do (soft kill switch).

The issue does not get triggered by the following loop (I may leave it
for several hours to get a better picture and modify to wait more
intelligently):

➜  ~ while test 1 ; do rfkill block 1 ; sleep 10 ; rfkill unblock 1 ; sleep 10 
; done
сен 05 01:26:13 blade kernel: wlp59s0: deauthenticating from 18:d6:c7:b0:26:ee 
by local choice (Reason: 3=DEAUTH_LEAVING)
сен 05 01:26:24 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:26:24 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:26:29 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:26:29 blade kernel: wlp59s0: authenticate with 18:d6:c7:b0:26:ee
сен 05 01:26:29 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 1/3)
сен 05 01:26:29 blade kernel: wlp59s0: authenticated
сен 05 01:26:29 blade kernel: wlp59s0: associate with 18:d6:c7:b0:26:ee (try 
1/3)
сен 05 01:26:29 blade kernel: wlp59s0: RX AssocResp from 18:d6:c7:b0:26:ee 
(capab=0x431 status=0 aid=1)
сен 05 01:26:29 blade kernel: wlp59s0: associated
сен 05 01:26:29 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link 
becomes ready
сен 05 01:26:33 blade kernel: wlp59s0: deauthenticating from 18:d6:c7:b0:26:ee 
by local choice (Reason: 3=DEAUTH_LEAVING)
сен 05 01:26:44 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:26:44 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:26:49 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:26:49 blade kernel: wlp59s0: authenticate with 18:d6:c7:b0:26:ee
сен 05 01:26:49 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 1/3)
сен 05 01:26:49 blade kernel: wlp59s0: authenticated
сен 05 01:26:49 blade kernel: wlp59s0: associate with 18:d6:c7:b0:26:ee (try 
1/3)
сен 05 01:26:49 blade kernel: wlp59s0: RX AssocResp from 18:d6:c7:b0:26:ee 
(capab=0x431 status=0 aid=1)
сен 05 01:26:49 blade kernel: wlp59s0: associated
сен 05 01:26:49 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link 
becomes ready
сен 05 01:26:53 blade kernel: wlp59s0: deauthenticating from 18:d6:c7:b0:26:ee 
by local choice (Reason: 3=DEAUTH_LEAVING)
сен 05 01:27:04 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:27:04 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:27:09 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:27:09 blade kernel: wlp59s0: authenticate with 18:d6:c7:b0:26:ee
сен 05 01:27:09 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 1/3)
сен 05 01:27:09 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 2/3)
сен 05 01:27:09 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 3/3)
сен 05 01:27:09 blade kernel: wlp59s0: authentication with 18:d6:c7:b0:26:ee 
timed out
сен 05 01:27:10 blade kernel: wlp59s0: authenticate with d8:74:95:e5:88:38
сен 05 01:27:10 blade kernel: wlp59s0: send auth to d8:74:95:e5:88:38 (try 1/3)
сен 05 01:27:10 blade kernel: wlp59s0: authenticated
сен 05 01:27:10 blade kernel: wlp59s0: associate with d8:74:95:e5:88:38 (try 
1/3)
сен 05 01:27:10 blade kernel: wlp59s0: RX AssocResp from d8:74:95:e5:88:38 
(capab=0x411 status=0 aid=4)
сен 05 01:27:10 blade kernel: wlp59s0: associated
сен 05 01:27:10 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link 
becomes ready
сен 05 01:27:14 blade kernel: wlp59s0: deauthenticating from d8:74:95:e5:88:38 
by local choice (Reason: 3=DEAUTH_LEAVING)
сен 05 01:27:24 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:27:25 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:27:29 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not 
ready
сен 05 01:27:29 blade kernel: wlp59s0: authenticate with 18:d6:c7:b0:26:ee
сен 05 01:27:29 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 1/3)
сен 05 01:27:29 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 2/3)
сен 05 01:27:29 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 3/3)
сен 05 01:27:29 blade kernel: wlp59s0: authentication with 18:d6:c7:b0:26:ee 
timed out
сен 05 01:27:30 blade kernel: wlp59s0: authenticate with d8:74:95:e5:88:38
сен 05 01:27:30 blade kernel: wlp59s0: send auth to d8:74:95:e5:88:38 (try 1/3)
сен 05 01:27:30 blade kernel: wlp59s0: authenticated
сен 05 01:27:30 blade kernel: wlp59s0: associate with d8:74:95:e5:88:38 (try 
1/3)
сен 05 01:27:30 blade kernel: wlp59s0: RX AssocResp from d8:74:95:e5:88:38 
(capab=0x411 status=0 aid=4)
сен 05 01:27:30 blade kernel: wlp59s0: associated
сен 05 01:27:30 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link 
becomes ready
сен 05 01:27:34 blade kernel: wlp59s0: deauthenticating from d8:74:95:e5:88:38 
by local choice (Reason: 3=DEAUTH_LEAVING)
сен 05 01:27:44 blade kernel: usb 1-1: 

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Kai-Heng Feng]

Seems like the PCI device no longer responds, so there are lots of
-ETIMEDOUT.

Does same thing happen when you press the wireless on/off hotkey?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Dmitrii Shcherbakov]

** Attachment added: "ath10k-repro4.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+attachment/4943912/+files/ath10k-repro4.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Dmitrii Shcherbakov]

Got a repro on 4.13.0-041300rc7 with the debug mask above set.

** Attachment added: "ath10k-repro3.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+attachment/4942967/+files/ath10k-repro3.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Kai-Heng Feng]

Add "ath10k_core.debug_mask=0x4041" to kernel parameter and attach dmesg
when the issue happens.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670706

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs