netdev - Fwd: Dell XPS 13 ath10k_pci firmware crashed!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <2db51694-aa57-cbfd-096e-4925b76232b0@gmail.com>
Date: Wed, 14 Jun 2023 08:15:24 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Kalle Valo <kvalo@...nel.org>, Thorsten Leemhuis <linux@...mhuis.info>,
 Garry Williams <gtwilliams@...il.com>
Cc: Linux Atheros 10K <ath10k@...ts.infradead.org>,
 Linux Wireless <linux-wireless@...r.kernel.org>,
 Linux Kernel Network Developers <netdev@...r.kernel.org>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Regressions <regressions@...ts.linux.dev>
Subject: Fwd: Dell XPS 13 ath10k_pci firmware crashed!

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> Beginning with kernel 6.2.15-300.fc38.x86_64 and continuing through 6.3.7-200.fc38.x86_64, the wifi connection fails periodically with these log messages:
> 
> ath10k_pci 0000:02:00.0: firmware crashed! (guid 6c545da0-593c-4a0e-b5ad-3ef2b91cdebf)
> ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
> ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
> ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00288- api 6 features wowlan,ignore-otp,mfp crc32 bf907c7c
> ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 d2863f91
> ath10k_pci 0000:02:00.0: htt-ver 3.87 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
> ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
> ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
> ath10k_pci 0000:02:00.0: Copy Engine register dump:
> ath10k_pci 0000:02:00.0: [00]: 0x00034400  12  12   3   3
> ath10k_pci 0000:02:00.0: [01]: 0x00034800  14  14 347 348
> ath10k_pci 0000:02:00.0: [02]: 0x00034c00   8   2   0   1
> ath10k_pci 0000:02:00.0: [03]: 0x00035000  16  15  16  14
> ath10k_pci 0000:02:00.0: [04]: 0x00035400 2995 2987  22 214
> ath10k_pci 0000:02:00.0: [05]: 0x00035800   0   0  64   0
> ath10k_pci 0000:02:00.0: [06]: 0x00035c00   0   0  18  18
> ath10k_pci 0000:02:00.0: [07]: 0x00036000   1   1   1   0
> ath10k_pci 0000:02:00.0: could not request stats (-108)
> ath10k_pci 0000:02:00.0: could not request peer stats info: -108
> ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
> ieee80211 phy0: Hardware restart was requested
> ath10k_pci 0000:02:00.0: could not request stats (-108)
> ath10k_pci 0000:02:00.0: device successfully recovered
> 
> 
> If I disconnect and reconnect using network manager, the connection is restored.  But this same failure recurs over and over after some few minutes to a few hours.
> 
> This is a regression.  The error was not reported with any previous kernel since 6.2.14-300.fc38.x86_64

See Bugzilla for the full thread.

Unfortunately, the reporter can't bisect this regression (he only tries
distribution kernels instead).

Anyway, I'm adding it to regzbot (as mainline regression because v6.2.x
has already EOL):

#regzbot introduced: v6.2..v6.3 https://bugzilla.kernel.org/show_bug.cgi?id=217549
#regzbot title: ath10k_pci firmware crashed on Dell XPS 13

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217549

-- 
An old man doll... just what I always wanted! - Clara