Bug #1670706 “Kernel Call Trace After Disabling an ath10k Wirele...” : Bugs : linux package : Ubuntu

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-03-07:

#1

AlsaInfo.txt Edit (37.5 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (426 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (232.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (361 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (128.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (18.8 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (874 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (9.0 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (325 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (5.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (8.1 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (20.8 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (227.1 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (584.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Brad Figg (brad-figg) wrote on 2017-03-07: Status changed to Confirmed

#2

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2017-03-07: Re: Kernel Call Trace After Disabling an ath10k Wireless Device

#3

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.11 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.11-rc1/

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Incomplete

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-03-07:

#4

Cannot reliably reproduce it even on the same kernel - will keep trying.

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-03-15:

#5

Reproduced on 4.10.0-11-generic after a long period of laptop inactivity (see traces at the bottom).

https://paste.ubuntu.com/24184748/

Tried to unload and reload modules afterwards:

[99449.709484] ath10k_pci 0000:3b:00.0: failed to read device register, device is gone
[99449.709487] ath10k_pci 0000:3b:00.0: failed to reset chip: -5
[99449.710036] ath10k_pci: probe of 0000:3b:00.0 failed with error -5

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-05-15:

#6

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

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Joseph Salisbury (jsalisbury) on 2017-05-15

Changed in linux (Ubuntu):
status:	Expired → Incomplete
tags:	added: kernel-da-key

Launchpad Janitor (janitor) on 2017-07-15

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-07-16:

#8

Download full text (10.8 KiB)

Still getting the same on the released 4.12 kernel.

Observations this time:

* Within a good range of an access point
* No power events (haven't closed a lid or anything like that)
* No high load no the wireless card

[12920.203097] usbcore: registered new interface driver snd-usb-audio
[15764.155095] perf: interrupt took too long (2522 > 2500), lowering kernel.perf_event_max_sample_rate to 79250

# no messages at all for a while

[17837.193714] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000a0b at 0x0003543c: -110
[17838.346474] ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
[17840.125795] ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110

[18026.693944] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c19 at 0x0003543c: -110
[18027.359637] ath10k_pci 0000:3b:00.0: failed to start hw scan: -11
[18027.717997] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c1b at 0x0003543c: -110
[18028.741757] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c1d at 0x0003543c: -110
[18029.765882] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c1f at 0x0003543c: -110
[18030.788925] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c21 at 0x0003543c: -110
[18031.455584] ath10k_pci 0000:3b:00.0: failed to start hw scan: -11
[18031.809091] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c23 at 0x0003543c: -110
[18032.837767] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c25 at 0x0003543c: -110
[18033.861726] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c27 at 0x0003543c: -110
[18034.783615] ath10k_pci 0000:3b:00.0: failed to delete WMI vdev 1: -11
[18034.885704] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c29 at 0x0003543c: -110
[18035.909919] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c2b at 0x0003543c: -110
[18036.933988] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c2d at 0x0003543c: -110
[18037.855672] ath10k_pci 0000:3b:00.0: failed to set 2g txpower 20: -11
[18037.855676] ath10k_pci 0000:3b:00.0: failed to setup tx power 20: -11
[18037.855679] ath10k_pci 0000:3b:00.0: failed to recalc tx power: -11
[18037.961916] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c2f at 0x0003543c: -110
[18038.981786] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c31 at 0x0003543c: -110
[18040.005258] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c33 at 0x0003543c: -110
[18040.927892] ath10k_pci 0000:3b:00.0: failed to set inactivity time for vdev 0: -11
[18040.927896] ath10k_pci 0000:3b:00.0: failed to setup powersave: -11
[18040.927921] wlp59s0: deauthenticating from 2c:e6:cc:27:91:68 by local choice (Reason: 3=DEAUTH_LEAVING)
[18041.029995] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c35 at 0x0003543c: -110
[18042.054088] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c37 at 0x0003543c: -110
[18043.077916] ath10k_pci 0000:3b:00.0: failed to...

Still getting the same on the released 4.12 kernel.

Observations this time:

* Within a good range of an access point
* No power events (haven't closed a lid or anything like that)
* No high load no the wireless card

[12920.203097] usbcore: registered new interface driver snd-usb-audio
[15764.155095] perf: interrupt took too long (2522 > 2500), lowering kernel.perf_event_max_sample_rate to 79250

# no messages at all for a while

[17837.193714] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000a0b at 0x0003543c: -110
[17838.346474] ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
[17840.125795] ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110

[18026.693944] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c19 at 0x0003543c: -110
[18027.359637] ath10k_pci 0000:3b:00.0: failed to start hw scan: -11
[18027.717997] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c1b at 0x0003543c: -110
[18028.741757] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c1d at 0x0003543c: -110
[18029.765882] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c1f at 0x0003543c: -110
[18030.788925] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c21 at 0x0003543c: -110
[18031.455584] ath10k_pci 0000:3b:00.0: failed to start hw scan: -11
[18031.809091] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c23 at 0x0003543c: -110
[18032.837767] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c25 at 0x0003543c: -110
[18033.861726] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c27 at 0x0003543c: -110
[18034.783615] ath10k_pci 0000:3b:00.0: failed to delete WMI vdev 1: -11
[18034.885704] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c29 at 0x0003543c: -110
[18035.909919] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c2b at 0x0003543c: -110
[18036.933988] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c2d at 0x0003543c: -110
[18037.855672] ath10k_pci 0000:3b:00.0: failed to set 2g txpower 20: -11
[18037.855676] ath10k_pci 0000:3b:00.0: failed to setup tx power 20: -11
[18037.855679] ath10k_pci 0000:3b:00.0: failed to recalc tx power: -11
[18037.961916] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c2f at 0x0003543c: -110
[18038.981786] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c31 at 0x0003543c: -110
[18040.005258] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c33 at 0x0003543c: -110
[18040.927892] ath10k_pci 0000:3b:00.0: failed to set inactivity time for vdev 0: -11
[18040.927896] ath10k_pci 0000:3b:00.0: failed to setup powersave: -11
[18040.927921] wlp59s0: deauthenticating from 2c:e6:cc:27:91:68 by local choice (Reason: 3=DEAUTH_LEAVING)
[18041.029995] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c35 at 0x0003543c: -110
[18042.054088] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c37 at 0x0003543c: -110
[18043.077916] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c39 at 0x0003543c: -110
[18043.999718] ath10k_pci 0000:3b:00.0: failed to set inactivity time for vdev 0: -11
[18043.999722] ath10k_pci 0000:3b:00.0: failed to setup powersave: -11
[18044.101753] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c3b at 0x0003543c: -110
[18045.125997] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c3d at 0x0003543c: -110
[18046.150186] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c3f at 0x0003543c: -110
[18047.071748] ath10k_pci 0000:3b:00.0: failed to set PS Mode 0 for vdev 0: -11
[18047.071752] ath10k_pci 0000:3b:00.0: failed to setup powersave: -11
[18047.071755] ath10k_pci 0000:3b:00.0: failed to setup ps on vdev 0: -11
[18047.109996] ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000c41 at 0x0003543c: -110
[18052.191759] ath10k_pci 0000:3b:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[18055.263791] ath10k_pci 0000:3b:00.0: failed to delete peer 2c:e6:cc:27:91:68 for vdev 0: -11
[18055.263798] ath10k_pci 0000:3b:00.0: found sta peer 2c:e6:cc:27:91:68 (ptr 0000000000000000 id 195) entry on vdev 0 after it was supposedly removed
[18055.263851] BUG: unable to handle kernel paging request at ffffffffc1505787
[18055.263942] IP: report_bug+0x94/0x120
[18055.263978] PGD 21040c067 
[18055.263980] P4D 21040c067 
[18055.264008] PUD 21040e067 
[18055.264035] PMD 46eeba067 
[18055.264062] PTE 800000046eb5a161
[18055.264139] Oops: 0003 [#1] SMP
[18055.264170] Modules linked in: snd_usb_audio snd_usbmidi_lib cmac rfcomm xt_conntrack ipt_REJECT nf_reject_ipv4 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bbswitch(OE) ipmi_devintf ipmi_msghandler bnep arc4 hid_rmi rmi_core binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic 8250_dw i2c_designware_platform i2c_designware_core mxm_wmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl x86_pkg_temp_thermal intel_powerclamp ath10k_pci snd_seq
[18055.264817]  coretemp ath10k_core ath kvm_intel uvcvideo kvm snd_seq_device snd_timer irqbypass videobuf2_vmalloc snd mac80211 intel_cstate videobuf2_memops videobuf2_v4l2 intel_rapl_perf serio_raw soundcore videobuf2_core btusb hci_uart btrtl cfg80211 btqca joydev btbcm videodev btintel mei_me input_leds media intel_pch_thermal idma64 bluetooth virt_dma mei intel_lpss_pci shpchp ecdh_generic wmi acpi_als intel_lpss_acpi intel_lpss acpi_pad kfifo_buf mac_hid tpm_crb industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc hid_generic aesni_intel i915 aes_x86_64 crypto_simd glue_helper cryptd psmouse i2c_algo_bit drm_kms_helper nvme syscopyarea nvme_core sysfillrect sysimgblt fb_sys_fops
[18055.265482]  drm usbhid i2c_hid hid video pinctrl_sunrisepoint pinctrl_intel [last unloaded: nvidia]
[18055.265575] CPU: 1 PID: 1430 Comm: NetworkManager Tainted: P           OE   4.12.0-custom #1
[18055.265649] Hardware name: Razer Blade/Razer, BIOS 1.00 01/10/2017
[18055.265705] task: ffff8b39ba164500 task.stack: ffff97edc31d0000
[18055.265763] RIP: 0010:report_bug+0x94/0x120
[18055.265803] RSP: 0018:ffff97edc31d3718 EFLAGS: 00010202
[18055.265852] RAX: 0000000000000907 RBX: ffff97edc31d3888 RCX: ffffffffc150577d
[18055.265916] RDX: 0000000000000001 RSI: 00000000000003c9 RDI: 0000000000000001
[18055.265979] RBP: ffff97edc31d3738 R08: ffff97edc31d4000 R09: 00000000000003c6
[18055.266043] R10: ffffffffb1206a80 R11: 0000000000000500 R12: ffffffffc148b0b6
[18055.266106] R13: ffffffffc1502a78 R14: 0000000000000006 R15: 0000000000000004
[18055.266171] FS:  00007f982ec41540(0000) GS:ffff8b39cec80000(0000) knlGS:0000000000000000
[18055.266243] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[18055.266295] CR2: ffffffffc1505787 CR3: 0000000475172000 CR4: 00000000003406e0
[18055.266358] Call Trace:
[18055.266420]  ? __sta_info_destroy_part2+0x166/0x170 [mac80211]
[18055.266479]  fixup_bug+0x2c/0x50
[18055.266515]  do_trap+0xa4/0x170
[18055.266550]  do_error_trap+0x89/0x110
[18055.266612]  ? __sta_info_destroy_part2+0x166/0x170 [mac80211]
[18055.266679]  ? ath10k_warn+0x8b/0x100 [ath10k_core]
[18055.266735]  ? ath10k_sta_state+0x16c/0xab0 [ath10k_core]
[18055.266787]  ? kfree+0x14a/0x160
[18055.266823]  do_invalid_op+0x20/0x30
[18055.266862]  invalid_op+0x1e/0x30
[18055.266922] RIP: 0010:__sta_info_destroy_part2+0x166/0x170 [mac80211]
[18055.266979] RSP: 0018:ffff97edc31d3930 EFLAGS: 00010286
[18055.267029] RAX: 00000000fffffff5 RBX: ffff8b3932b5c000 RCX: 0000000000000000
[18055.267092] RDX: ffff8b39ba164500 RSI: 0000000000000000 RDI: 0000000000000000
[18055.267155] RBP: ffff97edc31d3950 R08: ffff8b3922e0a600 R09: 000000018010000e
[18055.267219] R10: ffff97edc31d3840 R11: 0000000000000500 R12: ffff8b39b9c40780
[18055.267286] R13: ffff8b39b76868c0 R14: ffff8b39b76868c0 R15: ffff8b39b9c40cd0
[18055.267378]  __sta_info_flush+0xf5/0x190 [mac80211]
[18055.267463]  ieee80211_set_disassoc+0xb7/0x3b0 [mac80211]
[18055.267549]  ieee80211_mgd_deauth+0x276/0x430 [mac80211]
[18055.267632]  ieee80211_deauth+0x18/0x20 [mac80211]
[18055.267710]  cfg80211_mlme_deauth+0xaf/0x1d0 [cfg80211]
[18055.267786]  cfg80211_mlme_down+0x66/0x80 [cfg80211]
[18055.267860]  cfg80211_disconnect+0x19d/0x1b0 [cfg80211]
[18055.267928]  __cfg80211_leave+0x118/0x170 [cfg80211]
[18055.267994]  cfg80211_leave+0x2b/0x40 [cfg80211]
[18055.268057]  cfg80211_netdev_notifier_call+0x440/0x620 [cfg80211]
[18055.268123]  ? ath10k_monitor_recalc+0x11c/0x560 [ath10k_core]
[18055.268186]  ? ath10k_config_ps+0x52/0x70 [ath10k_core]
[18055.268238]  ? inetdev_event+0x47/0x4c0
[18055.268278]  ? skb_dequeue+0x59/0x70
[18055.268315]  notifier_call_chain+0x4a/0x70
[18055.268356]  raw_notifier_call_chain+0x16/0x20
[18055.268401]  call_netdevice_notifiers_info+0x35/0x60
[18055.268451]  __dev_close_many+0x5a/0x100
[18055.271928]  dev_close_many+0x8c/0x130
[18055.275446]  dev_close.part.88+0x4a/0x70
[18055.278898]  dev_close+0x1a/0x20
[18055.282366]  cfg80211_shutdown_all_interfaces+0x49/0xc0 [cfg80211]
[18055.285889]  cfg80211_rfkill_set_block+0x26/0x30 [cfg80211]
[18055.289422]  rfkill_set_block+0x90/0x160
[18055.293050]  rfkill_fop_write+0x117/0x1c0
[18055.296239]  __vfs_write+0x37/0x160
[18055.298621]  ? __fd_install+0x30/0xd0
[18055.300813]  ? apparmor_file_permission+0x1a/0x20
[18055.302466]  ? security_file_permission+0x3b/0xc0
[18055.304042]  vfs_write+0xb5/0x1a0
[18055.305543]  SyS_write+0x55/0xc0
[18055.306684]  ? SyS_fcntl+0x5d/0xb0
[18055.307769]  entry_SYSCALL_64_fastpath+0x1e/0xa9
[18055.308796] RIP: 0033:0x7f982c83b68d
[18055.309766] RSP: 002b:00007ffdda081e20 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
[18055.310708] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f982c83b68d
[18055.311518] RDX: 0000000000000008 RSI: 00007ffdda081e38 RDI: 0000000000000014
[18055.312322] RBP: 00007ffdda081f18 R08: 0000000000000020 R09: 0000000000000020
[18055.313123] R10: 0000000000000000 R11: 0000000000000293 R12: 00007f982ec412e0
[18055.313930] R13: 000055cd1c726ef0 R14: 000055cd1b254d28 R15: 0000000000000000
[18055.314729] Code: 74 59 0f b7 41 0a 4c 63 69 04 0f b7 71 08 89 c7 49 01 cd 83 e7 01 a8 02 74 15 66 85 ff 74 10 a8 04 ba 01 00 00 00 75 26 83 c8 04 <66> 89 41 0a 66 85 ff 74 49 0f b6 49 0b 4c 89 e2 45 31 c9 49 89 
[18055.315611] RIP: report_bug+0x94/0x120 RSP: ffff97edc31d3718
[18055.316366] CR2: ffffffffc1505787
[18055.323055] ---[ end trace 3da0da4ae101de81 ]---

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-07-16:

#9

dmesg-4.12-custom-ath10k-repro3.log Edit (115.9 KiB, text/plain)

Changed in linux (Ubuntu):
status:	Expired → New
summary:	- Kernel Call Trace After Disabling an ath10k Wireless Device + Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros + QCA6174 802.11ac (rev 32))

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2017-07-16: Status changed to Confirmed

#10

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2017-07-17:

#11

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

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-09-02:

#12

ath10k-repro3.log Edit (85.2 KiB, text/plain)

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

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-09-04:

#13

ath10k-repro4.log Edit (564.2 KiB, text/html)

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2017-09-04:

#14

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?

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-09-05:

#15

Download full text (11.8 KiB)

I don't have a special wireless off/on button on my keyboard but I'm assuming rfkill <block|unblock> <id> 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 kerne...

I don't have a special wireless off/on button on my keyboard but I'm assuming rfkill <block|unblock> <id> 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: USB disconnect, device number 8
сен 05 01:27:45 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:27:45 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:27:49 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:27:50 blade kernel: wlp59s0: authenticate with d8:74:95:e5:88:38
сен 05 01:27:50 blade kernel: wlp59s0: send auth to d8:74:95:e5:88:38 (try 1/3)
сен 05 01:27:50 blade kernel: wlp59s0: authenticated
сен 05 01:27:50 blade kernel: wlp59s0: associate with d8:74:95:e5:88:38 (try 1/3)
сен 05 01:27:50 blade kernel: wlp59s0: RX AssocResp from d8:74:95:e5:88:38 (capab=0x411 status=0 aid=4)
сен 05 01:27:50 blade kernel: wlp59s0: associated
сен 05 01:27:50 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready
сен 05 01:27:54 blade kernel: wlp59s0: deauthenticating from d8:74:95:e5:88:38 by local choice (Reason: 3=DEAUTH_LEAVING)
сен 05 01:28:05 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:28:05 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:28:06 blade kernel: usb 1-1: new high-speed USB device number 10 using xhci_hcd
сен 05 01:28:06 blade kernel: usb 1-1: New USB device found, idVendor=0fce, idProduct=01ba
сен 05 01:28:06 blade kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
сен 05 01:28:06 blade kernel: usb 1-1: Product: D6633
сен 05 01:28:06 blade kernel: usb 1-1: Manufacturer: Sony
сен 05 01:28:06 blade kernel: usb 1-1: SerialNumber: CB5A217QLS
сен 05 01:28:10 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:28:10 blade kernel: wlp59s0: authenticate with d8:74:95:e5:88:38
сен 05 01:28:10 blade kernel: wlp59s0: send auth to d8:74:95:e5:88:38 (try 1/3)
сен 05 01:28:10 blade kernel: wlp59s0: authenticated
сен 05 01:28:10 blade kernel: wlp59s0: associate with d8:74:95:e5:88:38 (try 1/3)
сен 05 01:28:10 blade kernel: wlp59s0: RX AssocResp from d8:74:95:e5:88:38 (capab=0x411 status=0 aid=4)
сен 05 01:28:10 blade kernel: wlp59s0: associated
сен 05 01:28:10 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready
сен 05 01:28:14 blade kernel: wlp59s0: deauthenticating from d8:74:95:e5:88:38 by local choice (Reason: 3=DEAUTH_LEAVING)
сен 05 01:28:25 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:28:25 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:28:30 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:28:30 blade kernel: wlp59s0: authenticate with d8:74:95:e5:88:38
сен 05 01:28:30 blade kernel: wlp59s0: send auth to d8:74:95:e5:88:38 (try 1/3)
сен 05 01:28:30 blade kernel: wlp59s0: authenticated
сен 05 01:28:30 blade kernel: wlp59s0: associate with d8:74:95:e5:88:38 (try 1/3)
сен 05 01:28:30 blade kernel: wlp59s0: RX AssocResp from d8:74:95:e5:88:38 (capab=0x411 status=0 aid=4)
сен 05 01:28:30 blade kernel: wlp59s0: associated
сен 05 01:28:30 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready
сен 05 01:28:34 blade kernel: wlp59s0: deauthenticating from d8:74:95:e5:88:38 by local choice (Reason: 3=DEAUTH_LEAVING)
сен 05 01:28:45 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:28:45 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:28:50 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:28:50 blade kernel: wlp59s0: authenticate with d8:74:95:e5:88:38
сен 05 01:28:50 blade kernel: wlp59s0: send auth to d8:74:95:e5:88:38 (try 1/3)
сен 05 01:28:50 blade kernel: wlp59s0: authenticated
сен 05 01:28:50 blade kernel: wlp59s0: associate with d8:74:95:e5:88:38 (try 1/3)
сен 05 01:28:50 blade kernel: wlp59s0: RX AssocResp from d8:74:95:e5:88:38 (capab=0x411 status=0 aid=2)
сен 05 01:28:50 blade kernel: wlp59s0: associated
сен 05 01:28:50 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready
сен 05 01:28:54 blade kernel: wlp59s0: deauthenticating from d8:74:95:e5:88:38 by local choice (Reason: 3=DEAUTH_LEAVING)
сен 05 01:29:05 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:29:05 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:29:10 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:29:10 blade kernel: wlp59s0: authenticate with 18:d6:c7:b0:26:ee
сен 05 01:29:10 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 1/3)
сен 05 01:29:10 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 2/3)
сен 05 01:29:10 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 3/3)
сен 05 01:29:10 blade kernel: wlp59s0: authentication with 18:d6:c7:b0:26:ee timed out
сен 05 01:29:10 blade kernel: wlp59s0: authenticate with d8:74:95:e5:88:38
сен 05 01:29:10 blade kernel: wlp59s0: send auth to d8:74:95:e5:88:38 (try 1/3)
сен 05 01:29:10 blade kernel: wlp59s0: authenticated
сен 05 01:29:10 blade kernel: wlp59s0: associate with d8:74:95:e5:88:38 (try 1/3)
сен 05 01:29:10 blade kernel: wlp59s0: RX AssocResp from d8:74:95:e5:88:38 (capab=0x411 status=0 aid=2)
сен 05 01:29:10 blade kernel: wlp59s0: associated
сен 05 01:29:10 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready
сен 05 01:29:14 blade kernel: wlp59s0: deauthenticating from d8:74:95:e5:88:38 by local choice (Reason: 3=DEAUTH_LEAVING)
сен 05 01:29:25 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:29:25 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:29:30 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:29:30 blade kernel: wlp59s0: authenticate with d8:74:95:e5:88:38
сен 05 01:29:30 blade kernel: wlp59s0: send auth to d8:74:95:e5:88:38 (try 1/3)
сен 05 01:29:30 blade kernel: wlp59s0: authenticated
сен 05 01:29:30 blade kernel: wlp59s0: associate with d8:74:95:e5:88:38 (try 1/3)
сен 05 01:29:30 blade kernel: wlp59s0: RX AssocResp from d8:74:95:e5:88:38 (capab=0x411 status=0 aid=2)
сен 05 01:29:30 blade kernel: wlp59s0: associated
сен 05 01:29:30 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready
сен 05 01:29:34 blade kernel: wlp59s0: deauthenticating from d8:74:95:e5:88:38 by local choice (Reason: 3=DEAUTH_LEAVING)
сен 05 01:29:45 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:29:45 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:29:50 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
сен 05 01:29:50 blade kernel: wlp59s0: authenticate with d8:74:95:e5:88:38
сен 05 01:29:50 blade kernel: wlp59s0: send auth to d8:74:95:e5:88:38 (try 1/3)
сен 05 01:29:50 blade kernel: wlp59s0: authenticated
сен 05 01:29:50 blade kernel: wlp59s0: associate with d8:74:95:e5:88:38 (try 1/3)
сен 05 01:29:50 blade kernel: wlp59s0: RX AssocResp from d8:74:95:e5:88:38 (capab=0x411 status=0 aid=2)
сен 05 01:29:50 blade kernel: wlp59s0: associated
сен 05 01:29:50 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready
^C%

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2017-09-05:

#16

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 0000:08:00.0: Host halt failed, -19
мар 07 01:54:21 hostname kernel: xhci_hcd 0000: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?

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-09-05:

#17

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.

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-09-09:

#18

Download full text (3.7 KiB)

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
-[0000: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: ...

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     
-[0000: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

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-09-09:

#19

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.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2017-09-10:

#20

You mean both ax88179_178a and hid-rmi work?

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-09-10:

#21

type-c-device-razer-core.png Edit (190.4 KiB, image/png)

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-0000: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 0000:03:02.0: Refused to change power state, currently in D3
[18439.041917] pcieport 0000: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.

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-0000: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 0000:03:02.0: Refused to change power state, currently in D3
[18439.041917] pcieport 0000: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.

Revision history for this message

Dmitrii Shcherbakov (dmitriis) wrote on 2017-09-10:

#22

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

Revision history for this message

Gold Star (goldstar611) wrote on 2018-08-19:

#23

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.

Brad Figg (brad-figg) on 2019-07-24

tags:

added: cscc

Ubuntu
linux package

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

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntulinux package

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

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package