* Atheros QCA6174 ath10k_pci fimware crashing [not found] <1209906123.2716993.1695416371605.ref@mail.yahoo.com> @ 2023-09-22 20:59 ` Cool Goose 2023-09-23 0:20 ` Bagas Sanjaya 0 siblings, 1 reply; 9+ messages in thread From: Cool Goose @ 2023-09-22 20:59 UTC (permalink / raw) To: ath10k@lists.infradead.org Reference and more details https://bbs.archlinux.org/viewtopic.php?id=288991 $ sudo journalctl -b | grep ath10k | more Sep 19 07:43:58 hostname kernel: ath10k_pci 0000:03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Sep 19 07:43:58 hostname kernel: ath10k_pci 0000:03:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 17aa:0827 Sep 19 07:43:58 hostname kernel: ath10k_pci 0000:03:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0 Sep 19 07:43:58 hostname kernel: ath10k_pci 0000:03:00.0: firmware ver WLAN.RM.4.4.1-00157-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 90eebefb Sep 19 07:43:59 hostname kernel: ath10k_pci 0000:03:00.0: board_file api 2 bmi_id N/A crc32 706c395e Sep 19 07:43:59 hostname kernel: ath10k_pci 0000:03:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 Sep 19 07:43:59 hostname kernel: ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0 Sep 19 07:43:59 hostname NetworkManager[640]: <info> [1695123839.8991] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0/ieee80211/phy0/rfkill2) (driver ath10k_pci) Sep 19 08:11:42 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info Sep 19 08:11:47 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware Sep 19 08:11:47 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) Sep 19 08:11:47 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 Sep 19 08:11:47 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered Sep 19 08:15:54 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info Sep 19 08:15:59 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware Sep 19 08:15:59 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) Sep 19 08:15:59 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 Sep 19 08:15:59 hostname kernel: ath10k_pci 0000:03:00.0: failed to read hi_board_data address: -16 Sep 19 08:16:02 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive initialized event from target: 00000000 Sep 19 08:16:05 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive initialized event from target: 00000000 Sep 19 08:16:05 hostname kernel: ath10k_pci 0000:03:00.0: failed to wait for target init: -110 Sep 19 08:16:05 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-108) Sep 19 08:16:05 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered Sep 19 08:20:30 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive scan abortion completion: timed out Sep 19 08:20:30 hostname kernel: ath10k_pci 0000:03:00.0: failed to abort scan: -110 Sep 19 08:20:36 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90124 timeout, restarting hardware Sep 19 08:20:36 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -11 Sep 19 08:20:36 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered Sep 19 08:25:55 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive scan abortion completion: timed out Sep 19 08:25:55 hostname kernel: ath10k_pci 0000:03:00.0: failed to abort scan: -110 Sep 19 08:26:00 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90124 timeout, restarting hardware Sep 19 08:26:00 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -11 Sep 19 08:26:00 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered Sep 19 08:28:24 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info Sep 19 08:28:29 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware Sep 19 08:28:29 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) Sep 19 08:28:29 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 Sep 19 08:28:29 hostname kernel: ath10k_pci 0000:03:00.0: failed to read hi_board_data address: -16 Sep 19 08:28:32 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive initialized event from target: 00000000 Sep 19 08:28:35 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive initialized event from target: 00000000 Sep 19 08:28:35 hostname kernel: ath10k_pci 0000:03:00.0: failed to wait for target init: -110 Sep 19 08:28:35 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-108) Sep 19 08:28:35 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered Sep 19 08:35:24 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info Sep 19 08:35:29 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware Sep 19 08:35:29 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) Sep 19 08:35:29 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 Sep 19 08:35:29 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered Sep 19 08:39:42 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info Sep 19 08:39:47 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware Sep 19 08:39:47 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) Sep 19 08:39:47 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 Sep 19 08:39:47 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered Sep 19 09:00:31 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:32 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x0000000e at 0x0003503c: -110 Sep 19 09:00:32 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:33 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x0000000f at 0x0003503c: -110 Sep 19 09:00:36 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a000: -110 Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x00036040: -110 Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x0003603c: -110 Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:46 hostname kernel: ath10k_warn: 137 callbacks suppressed Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:00:51 hostname kernel: ath10k_warn: 135 callbacks suppressed Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xfffffffe at 0x00035c2c: -110 Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00035c34: -110 Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xfffff81f at 0x00035c34: -110 Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00035c2c: -110 Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xffffffe1 at 0x00035c2c: -110 Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x0003a008: -110 Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x0007fc00 at 0x0003a014: -110 Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a008: -110 Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a000: -110 Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xfffff7ff at 0x0003a000: -110 Sep 19 09:00:56 hostname kernel: ath10k_warn: 136 callbacks suppressed Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:00:57 hostname kernel: ath10k_pci 0000:03:00.0: failed to read device register, device is gone Sep 19 09:01:01 hostname kernel: ath10k_warn: 136 callbacks suppressed Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:03 hostname kernel: ath10k_pci 0000:03:00.0: failed to read device register, device is gone Sep 19 09:01:06 hostname kernel: ath10k_warn: 142 callbacks suppressed Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: failed to read device register, device is gone Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: failed to reset chip: -5 Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: Could not init hif: -5 Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: firmware crashed! (guid 181cebb0-7ef7-4f43-867d-f7c220de5e83) Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 17aa:0827 Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0 Sep 19 09:01:07 hostname kernel: Modules linked in: ccm dm_crypt cbc encrypted_keys trusted asn1_encoder tee serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic xts ecb algif_skcipher af_alg snd_soc_avs snd_soc_hda_codec intel_rapl_msr snd_soc_skl intel_rapl_common snd_hda_codec_hdmi snd_soc_hdac_hda intel_tcc_cooling snd_hda_ext_core x86_pkg_temp_thermal snd_soc_sst_ipc intel_powerclamp snd_soc_sst_dsp snd _soc_acpi_intel_match snd_soc_acpi coretemp snd_soc_core snd_hda_codec_realtek kvm_intel snd_hda_codec_generic snd_compress ac97_bus ledtrig_audio snd_pcm_dmaengine kvm joydev hid_sensor_accel_3d ath10k_pci rt2800usb hid_sensor_trigger snd_hda_intel industrialio_triggered_buffer irqbypass rt2x00usb ath10k_core mousedev snd_intel_dspcfg crct10dif_pclmul snd_intel_sdw_acpi rt2800lib kfifo_buf crc32_pclmul polyval_clmulni wac om hid_sensor_iio_common snd_hda_codec uvcvideo rt2x00lib ath polyval_generic industrialio hid_sensor_custom gf128mul snd_hda_core usbhid videobuf2_vmalloc Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: firmware ver WLAN.RM.4.4.1-00157-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 90eebefb Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: board_file api 2 bmi_id N/A crc32 706c395e Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 Sep 19 09:01:11 hostname kernel: Modules linked in: ccm dm_crypt cbc encrypted_keys trusted asn1_encoder tee serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic xts ecb algif_skcipher af_alg snd_soc_avs snd_soc_hda_codec intel_rapl_msr snd_soc_skl intel_rapl_common snd_hda_codec_hdmi snd_soc_hdac_hda intel_tcc_cooling snd_hda_ext_core x86_pkg_temp_thermal snd_soc_sst_ipc intel_powerclamp snd_soc_sst_dsp snd _soc_acpi_intel_match snd_soc_acpi coretemp snd_soc_core snd_hda_codec_realtek kvm_intel snd_hda_codec_generic snd_compress ac97_bus ledtrig_audio snd_pcm_dmaengine kvm joydev hid_sensor_accel_3d ath10k_pci rt2800usb hid_sensor_trigger snd_hda_intel industrialio_triggered_buffer irqbypass rt2x00usb ath10k_core mousedev snd_intel_dspcfg crct10dif_pclmul snd_intel_sdw_acpi rt2800lib kfifo_buf crc32_pclmul polyval_clmulni wac om hid_sensor_iio_common snd_hda_codec uvcvideo rt2x00lib ath polyval_generic industrialio hid_sensor_custom gf128mul snd_hda_core usbhid videobuf2_vmalloc Sep 19 09:01:11 hostname kernel: ath10k_warn: 149 callbacks suppressed Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Atheros QCA6174 ath10k_pci fimware crashing 2023-09-22 20:59 ` Atheros QCA6174 ath10k_pci fimware crashing Cool Goose @ 2023-09-23 0:20 ` Bagas Sanjaya 2023-09-25 10:08 ` Kalle Valo 0 siblings, 1 reply; 9+ messages in thread From: Bagas Sanjaya @ 2023-09-23 0:20 UTC (permalink / raw) To: Cool Goose, Linux ath10k; +Cc: Kalle Valo, Jeff Johnson [-- Attachment #1.1: Type: text/plain, Size: 17288 bytes --] On Fri, Sep 22, 2023 at 08:59:31PM +0000, Cool Goose wrote: > Reference and more details https://bbs.archlinux.org/viewtopic.php?id=288991 > > $ sudo journalctl -b | grep ath10k | more > Sep 19 07:43:58 hostname kernel: ath10k_pci 0000:03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 > Sep 19 07:43:58 hostname kernel: ath10k_pci 0000:03:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 17aa:0827 > Sep 19 07:43:58 hostname kernel: ath10k_pci 0000:03:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0 > Sep 19 07:43:58 hostname kernel: ath10k_pci 0000:03:00.0: firmware ver WLAN.RM.4.4.1-00157-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 90eebefb > Sep 19 07:43:59 hostname kernel: ath10k_pci 0000:03:00.0: board_file api 2 bmi_id N/A crc32 706c395e > Sep 19 07:43:59 hostname kernel: ath10k_pci 0000:03:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 > Sep 19 07:43:59 hostname kernel: ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0 > Sep 19 07:43:59 hostname NetworkManager[640]: <info> [1695123839.8991] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0/ieee80211/phy0/rfkill2) (driver ath10k_pci) > Sep 19 08:11:42 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info > Sep 19 08:11:47 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware > Sep 19 08:11:47 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) > Sep 19 08:11:47 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 > Sep 19 08:11:47 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered > Sep 19 08:15:54 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info > Sep 19 08:15:59 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware > Sep 19 08:15:59 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) > Sep 19 08:15:59 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 > Sep 19 08:15:59 hostname kernel: ath10k_pci 0000:03:00.0: failed to read hi_board_data address: -16 > Sep 19 08:16:02 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive initialized event from target: 00000000 > Sep 19 08:16:05 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive initialized event from target: 00000000 > Sep 19 08:16:05 hostname kernel: ath10k_pci 0000:03:00.0: failed to wait for target init: -110 > Sep 19 08:16:05 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-108) > Sep 19 08:16:05 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered > Sep 19 08:20:30 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive scan abortion completion: timed out > Sep 19 08:20:30 hostname kernel: ath10k_pci 0000:03:00.0: failed to abort scan: -110 > Sep 19 08:20:36 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90124 timeout, restarting hardware > Sep 19 08:20:36 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -11 > Sep 19 08:20:36 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered > Sep 19 08:25:55 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive scan abortion completion: timed out > Sep 19 08:25:55 hostname kernel: ath10k_pci 0000:03:00.0: failed to abort scan: -110 > Sep 19 08:26:00 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90124 timeout, restarting hardware > Sep 19 08:26:00 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -11 > Sep 19 08:26:00 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered > Sep 19 08:28:24 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info > Sep 19 08:28:29 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware > Sep 19 08:28:29 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) > Sep 19 08:28:29 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 > Sep 19 08:28:29 hostname kernel: ath10k_pci 0000:03:00.0: failed to read hi_board_data address: -16 > Sep 19 08:28:32 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive initialized event from target: 00000000 > Sep 19 08:28:35 hostname kernel: ath10k_pci 0000:03:00.0: failed to receive initialized event from target: 00000000 > Sep 19 08:28:35 hostname kernel: ath10k_pci 0000:03:00.0: failed to wait for target init: -110 > Sep 19 08:28:35 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-108) > Sep 19 08:28:35 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered > Sep 19 08:35:24 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info > Sep 19 08:35:29 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware > Sep 19 08:35:29 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) > Sep 19 08:35:29 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 > Sep 19 08:35:29 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered > Sep 19 08:39:42 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info > Sep 19 08:39:47 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware > Sep 19 08:39:47 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) > Sep 19 08:39:47 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 > Sep 19 08:39:47 hostname kernel: ath10k_pci 0000:03:00.0: device successfully recovered > Sep 19 09:00:31 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:32 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x0000000e at 0x0003503c: -110 > Sep 19 09:00:32 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:33 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x0000000f at 0x0003503c: -110 > Sep 19 09:00:36 hostname kernel: ath10k_pci 0000:03:00.0: timed out waiting peer stats info > Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: wmi command 90113 timeout, restarting hardware > Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: could not request stats (-11) > Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: could not request peer stats info: -108 > Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a000: -110 > Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x00036040: -110 > Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x0003603c: -110 > Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:41 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:46 hostname kernel: ath10k_warn: 137 callbacks suppressed > Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:46 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:00:51 hostname kernel: ath10k_warn: 135 callbacks suppressed > Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xfffffffe at 0x00035c2c: -110 > Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00035c34: -110 > Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xfffff81f at 0x00035c34: -110 > Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00035c2c: -110 > Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xffffffe1 at 0x00035c2c: -110 > Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x0003a008: -110 > Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x0007fc00 at 0x0003a014: -110 > Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a008: -110 > Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a000: -110 > Sep 19 09:00:51 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xfffff7ff at 0x0003a000: -110 > Sep 19 09:00:56 hostname kernel: ath10k_warn: 136 callbacks suppressed > Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:56 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:00:57 hostname kernel: ath10k_pci 0000:03:00.0: failed to read device register, device is gone > Sep 19 09:01:01 hostname kernel: ath10k_warn: 136 callbacks suppressed > Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:01 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:03 hostname kernel: ath10k_pci 0000:03:00.0: failed to read device register, device is gone > Sep 19 09:01:06 hostname kernel: ath10k_warn: 142 callbacks suppressed > Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:06 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110 > Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: failed to read device register, device is gone > Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: failed to reset chip: -5 > Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: Could not init hif: -5 > Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: firmware crashed! (guid 181cebb0-7ef7-4f43-867d-f7c220de5e83) > Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 17aa:0827 > Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0 > Sep 19 09:01:07 hostname kernel: Modules linked in: ccm dm_crypt cbc encrypted_keys trusted asn1_encoder tee serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic xts ecb algif_skcipher af_alg snd_soc_avs snd_soc_hda_codec intel_rapl_msr snd_soc_skl intel_rapl_common snd_hda_codec_hdmi snd_soc_hdac_hda intel_tcc_cooling snd_hda_ext_core x86_pkg_temp_thermal snd_soc_sst_ipc intel_powerclamp snd_soc_sst_dsp snd > _soc_acpi_intel_match snd_soc_acpi coretemp snd_soc_core snd_hda_codec_realtek kvm_intel snd_hda_codec_generic snd_compress ac97_bus ledtrig_audio snd_pcm_dmaengine kvm joydev hid_sensor_accel_3d ath10k_pci rt2800usb hid_sensor_trigger snd_hda_intel industrialio_triggered_buffer irqbypass rt2x00usb ath10k_core mousedev snd_intel_dspcfg crct10dif_pclmul snd_intel_sdw_acpi rt2800lib kfifo_buf crc32_pclmul polyval_clmulni wac > om hid_sensor_iio_common snd_hda_codec uvcvideo rt2x00lib ath polyval_generic industrialio hid_sensor_custom gf128mul snd_hda_core usbhid videobuf2_vmalloc > Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: firmware ver WLAN.RM.4.4.1-00157-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 90eebefb > Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: board_file api 2 bmi_id N/A crc32 706c395e > Sep 19 09:01:07 hostname kernel: ath10k_pci 0000:03:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 > Sep 19 09:01:11 hostname kernel: Modules linked in: ccm dm_crypt cbc encrypted_keys trusted asn1_encoder tee serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic xts ecb algif_skcipher af_alg snd_soc_avs snd_soc_hda_codec intel_rapl_msr snd_soc_skl intel_rapl_common snd_hda_codec_hdmi snd_soc_hdac_hda intel_tcc_cooling snd_hda_ext_core x86_pkg_temp_thermal snd_soc_sst_ipc intel_powerclamp snd_soc_sst_dsp snd > _soc_acpi_intel_match snd_soc_acpi coretemp snd_soc_core snd_hda_codec_realtek kvm_intel snd_hda_codec_generic snd_compress ac97_bus ledtrig_audio snd_pcm_dmaengine kvm joydev hid_sensor_accel_3d ath10k_pci rt2800usb hid_sensor_trigger snd_hda_intel industrialio_triggered_buffer irqbypass rt2x00usb ath10k_core mousedev snd_intel_dspcfg crct10dif_pclmul snd_intel_sdw_acpi rt2800lib kfifo_buf crc32_pclmul polyval_clmulni wac > om hid_sensor_iio_common snd_hda_codec uvcvideo rt2x00lib ath polyval_generic industrialio hid_sensor_custom gf128mul snd_hda_core usbhid videobuf2_vmalloc > Sep 19 09:01:11 hostname kernel: ath10k_warn: 149 callbacks suppressed > Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 > Looks like hardware issue, right? -- An old man doll... just what I always wanted! - Clara [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --] [-- Attachment #2: Type: text/plain, Size: 146 bytes --] _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Atheros QCA6174 ath10k_pci fimware crashing 2023-09-23 0:20 ` Bagas Sanjaya @ 2023-09-25 10:08 ` Kalle Valo 2023-09-25 10:15 ` Bagas Sanjaya 0 siblings, 1 reply; 9+ messages in thread From: Kalle Valo @ 2023-09-25 10:08 UTC (permalink / raw) To: Bagas Sanjaya; +Cc: Cool Goose, Linux ath10k, Jeff Johnson Bagas Sanjaya <bagasdotme@gmail.com> writes: >> Sep 19 09:01:11 hostname kernel: ath10k_warn: 149 callbacks suppressed >> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >> > > Looks like hardware issue, right? It could be a hardware issue (for example a problem with the PCI bus communication) but also simply a firmware crash. These kind of reports come time to time but root cause is unknown. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Atheros QCA6174 ath10k_pci fimware crashing 2023-09-25 10:08 ` Kalle Valo @ 2023-09-25 10:15 ` Bagas Sanjaya 0 siblings, 0 replies; 9+ messages in thread From: Bagas Sanjaya @ 2023-09-25 10:15 UTC (permalink / raw) To: Kalle Valo Cc: Cool Goose, Linux ath10k, Jeff Johnson, Linux Kernel Mailing List On 25/09/2023 17:08, Kalle Valo wrote: > Bagas Sanjaya <bagasdotme@gmail.com> writes: > >>> Sep 19 09:01:11 hostname kernel: ath10k_warn: 149 callbacks suppressed >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> >> >> Looks like hardware issue, right? > > It could be a hardware issue (for example a problem with the PCI bus > communication) but also simply a firmware crash. These kind of reports > come time to time but root cause is unknown. > The reporter said on Arch Linux forum (see TS) that trying older linux-firmware package doesn't help, so I suspect this as hardware issue. Cool Goose, what is your laptop model? -- An old man doll... just what I always wanted! - Clara _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Atheros QCA6174 ath10k_pci fimware crashing @ 2023-09-25 10:15 ` Bagas Sanjaya 0 siblings, 0 replies; 9+ messages in thread From: Bagas Sanjaya @ 2023-09-25 10:15 UTC (permalink / raw) To: Kalle Valo Cc: Cool Goose, Linux ath10k, Jeff Johnson, Linux Kernel Mailing List On 25/09/2023 17:08, Kalle Valo wrote: > Bagas Sanjaya <bagasdotme@gmail.com> writes: > >>> Sep 19 09:01:11 hostname kernel: ath10k_warn: 149 callbacks suppressed >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> >> >> Looks like hardware issue, right? > > It could be a hardware issue (for example a problem with the PCI bus > communication) but also simply a firmware crash. These kind of reports > come time to time but root cause is unknown. > The reporter said on Arch Linux forum (see TS) that trying older linux-firmware package doesn't help, so I suspect this as hardware issue. Cool Goose, what is your laptop model? -- An old man doll... just what I always wanted! - Clara ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Atheros QCA6174 ath10k_pci fimware crashing 2023-09-25 10:15 ` Bagas Sanjaya @ 2023-09-25 16:14 ` Cool Goose -1 siblings, 0 replies; 9+ messages in thread From: Cool Goose @ 2023-09-25 16:14 UTC (permalink / raw) To: Kalle Valo, Bagas Sanjaya Cc: Linux ath10k, Jeff Johnson, Linux Kernel Mailing List Laptop model : Lenovo Flex 5, running Arch Linux since Dec 2019. No issues til around late 2022 when I would just disable wireless and reenable from GNOME system tray NetworkManager applet and then things would work fine. But for almost a couple of months, constant firmware crashes and device cannot be recovered even after disable-renabling wireless. If I remember correctly the transition to constant crashes coincided with me upgrading system, thus I am reporting here. Just in case it helps, I tried looking for a small system journal from the laptop where the firmware crash was included, and posted that here. http://ix.io/4Hpr I am trying to find out if this actually looks like a hardware failure becuase in that case I can call it non-recoverable issue and look for a wifi adapter. If it is hardware failure, I am trying to find out if there are any card settings I can tweak in may be BIOS that would make it work in say a restricted mode. Thanks. On Monday, 25 September, 2023 at 06:15:27 am GMT-4, Bagas Sanjaya <bagasdotme@gmail.com> wrote: On 25/09/2023 17:08, Kalle Valo wrote: > Bagas Sanjaya <bagasdotme@gmail.com> writes: > >>> Sep 19 09:01:11 hostname kernel: ath10k_warn: 149 callbacks suppressed >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> >> >> Looks like hardware issue, right? > > It could be a hardware issue (for example a problem with the PCI bus > communication) but also simply a firmware crash. These kind of reports > come time to time but root cause is unknown. > The reporter said on Arch Linux forum (see TS) that trying older linux-firmware package doesn't help, so I suspect this as hardware issue. Cool Goose, what is your laptop model? -- An old man doll... just what I always wanted! - Clara _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Atheros QCA6174 ath10k_pci fimware crashing @ 2023-09-25 16:14 ` Cool Goose 0 siblings, 0 replies; 9+ messages in thread From: Cool Goose @ 2023-09-25 16:14 UTC (permalink / raw) To: Kalle Valo, Bagas Sanjaya Cc: Linux ath10k, Jeff Johnson, Linux Kernel Mailing List Laptop model : Lenovo Flex 5, running Arch Linux since Dec 2019. No issues til around late 2022 when I would just disable wireless and reenable from GNOME system tray NetworkManager applet and then things would work fine. But for almost a couple of months, constant firmware crashes and device cannot be recovered even after disable-renabling wireless. If I remember correctly the transition to constant crashes coincided with me upgrading system, thus I am reporting here. Just in case it helps, I tried looking for a small system journal from the laptop where the firmware crash was included, and posted that here. http://ix.io/4Hpr I am trying to find out if this actually looks like a hardware failure becuase in that case I can call it non-recoverable issue and look for a wifi adapter. If it is hardware failure, I am trying to find out if there are any card settings I can tweak in may be BIOS that would make it work in say a restricted mode. Thanks. On Monday, 25 September, 2023 at 06:15:27 am GMT-4, Bagas Sanjaya <bagasdotme@gmail.com> wrote: On 25/09/2023 17:08, Kalle Valo wrote: > Bagas Sanjaya <bagasdotme@gmail.com> writes: > >>> Sep 19 09:01:11 hostname kernel: ath10k_warn: 149 callbacks suppressed >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> >> >> Looks like hardware issue, right? > > It could be a hardware issue (for example a problem with the PCI bus > communication) but also simply a firmware crash. These kind of reports > come time to time but root cause is unknown. > The reporter said on Arch Linux forum (see TS) that trying older linux-firmware package doesn't help, so I suspect this as hardware issue. Cool Goose, what is your laptop model? -- An old man doll... just what I always wanted! - Clara ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Atheros QCA6174 ath10k_pci fimware crashing 2023-09-25 16:14 ` Cool Goose @ 2023-10-30 14:38 ` Cool Goose -1 siblings, 0 replies; 9+ messages in thread From: Cool Goose @ 2023-10-30 14:38 UTC (permalink / raw) To: Kalle Valo, Bagas Sanjaya Cc: Linux ath10k, Jeff Johnson, Linux Kernel Mailing List It does feel like a hardware issue, either the bus or the card. I had Windows dual boot on the laptop and even Windows is complaining of network issues. On Monday, 25 September, 2023 at 12:14:02 pm GMT-4, Cool Goose <coolgoose54@yahoo.in> wrote: Laptop model : Lenovo Flex 5, running Arch Linux since Dec 2019. No issues til around late 2022 when I would just disable wireless and reenable from GNOME system tray NetworkManager applet and then things would work fine. But for almost a couple of months, constant firmware crashes and device cannot be recovered even after disable-renabling wireless. If I remember correctly the transition to constant crashes coincided with me upgrading system, thus I am reporting here. Just in case it helps, I tried looking for a small system journal from the laptop where the firmware crash was included, and posted that here. http://ix.io/4Hpr I am trying to find out if this actually looks like a hardware failure becuase in that case I can call it non-recoverable issue and look for a wifi adapter. If it is hardware failure, I am trying to find out if there are any card settings I can tweak in may be BIOS that would make it work in say a restricted mode. Thanks. On Monday, 25 September, 2023 at 06:15:27 am GMT-4, Bagas Sanjaya <bagasdotme@gmail.com> wrote: On 25/09/2023 17:08, Kalle Valo wrote: > Bagas Sanjaya <bagasdotme@gmail.com> writes: > >>> Sep 19 09:01:11 hostname kernel: ath10k_warn: 149 callbacks suppressed >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> >> >> Looks like hardware issue, right? > > It could be a hardware issue (for example a problem with the PCI bus > communication) but also simply a firmware crash. These kind of reports > come time to time but root cause is unknown. > The reporter said on Arch Linux forum (see TS) that trying older linux-firmware package doesn't help, so I suspect this as hardware issue. Cool Goose, what is your laptop model? -- An old man doll... just what I always wanted! - Clara _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Atheros QCA6174 ath10k_pci fimware crashing @ 2023-10-30 14:38 ` Cool Goose 0 siblings, 0 replies; 9+ messages in thread From: Cool Goose @ 2023-10-30 14:38 UTC (permalink / raw) To: Kalle Valo, Bagas Sanjaya Cc: Linux ath10k, Jeff Johnson, Linux Kernel Mailing List It does feel like a hardware issue, either the bus or the card. I had Windows dual boot on the laptop and even Windows is complaining of network issues. On Monday, 25 September, 2023 at 12:14:02 pm GMT-4, Cool Goose <coolgoose54@yahoo.in> wrote: Laptop model : Lenovo Flex 5, running Arch Linux since Dec 2019. No issues til around late 2022 when I would just disable wireless and reenable from GNOME system tray NetworkManager applet and then things would work fine. But for almost a couple of months, constant firmware crashes and device cannot be recovered even after disable-renabling wireless. If I remember correctly the transition to constant crashes coincided with me upgrading system, thus I am reporting here. Just in case it helps, I tried looking for a small system journal from the laptop where the firmware crash was included, and posted that here. http://ix.io/4Hpr I am trying to find out if this actually looks like a hardware failure becuase in that case I can call it non-recoverable issue and look for a wifi adapter. If it is hardware failure, I am trying to find out if there are any card settings I can tweak in may be BIOS that would make it work in say a restricted mode. Thanks. On Monday, 25 September, 2023 at 06:15:27 am GMT-4, Bagas Sanjaya <bagasdotme@gmail.com> wrote: On 25/09/2023 17:08, Kalle Valo wrote: > Bagas Sanjaya <bagasdotme@gmail.com> writes: > >>> Sep 19 09:01:11 hostname kernel: ath10k_warn: 149 callbacks suppressed >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110 >>> >> >> Looks like hardware issue, right? > > It could be a hardware issue (for example a problem with the PCI bus > communication) but also simply a firmware crash. These kind of reports > come time to time but root cause is unknown. > The reporter said on Arch Linux forum (see TS) that trying older linux-firmware package doesn't help, so I suspect this as hardware issue. Cool Goose, what is your laptop model? -- An old man doll... just what I always wanted! - Clara ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2023-10-30 14:38 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1209906123.2716993.1695416371605.ref@mail.yahoo.com>
2023-09-22 20:59 ` Atheros QCA6174 ath10k_pci fimware crashing Cool Goose
2023-09-23 0:20 ` Bagas Sanjaya
2023-09-25 10:08 ` Kalle Valo
2023-09-25 10:15 ` Bagas Sanjaya
2023-09-25 10:15 ` Bagas Sanjaya
2023-09-25 16:14 ` Cool Goose
2023-09-25 16:14 ` Cool Goose
2023-10-30 14:38 ` Cool Goose
2023-10-30 14:38 ` Cool Goose
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.