linux-kernel - Re: ath10k_pci 0000:3a:00.0: Could not init core: -110

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <96828117-2cf8-4a34-a8e6-78ace96b32d3@molgen.mpg.de>
Date: Mon, 27 May 2024 12:24:59 +0200
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Kalle Valo <kvalo@...nel.org>, Baochen Qiang <quic_bqiang@...cinc.com>
Cc: linux-wireless@...r.kernel.org, ath10k@...ts.infradead.org,
 linux-kernel@...r.kernel.org, Hans de Goede <hdegoede@...hat.com>,
 James Prestwood <prestwoj@...il.com>
Subject: Re: ath10k_pci 0000:3a:00.0: Could not init core: -110

Dear Kalle, dear Baochen,


Am 27.05.24 um 11:10 schrieb Kalle Valo:
> Baochen Qiang writes:
> 
>> On 5/27/2024 4:42 PM, Paul Menzel wrote:

>>> On the Intel Kaby Lake notebook Dell XPS 13 with
>>>
>>>      3a:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
>>>
>>> with at least a self-built Linux 6.9-rc5, on April 26th, 2024, and
>>> Linux 6.8.11, today, May 27th, 2024, the error below happened, and
>>> the device couldn’t authenticate to a WiFi network until reloading
>>> the module *ath10k_core* and *ath10k_pci* (didn’t check just
>>> *ath10k_pci*):
>>>
>>>      $ sudo modprobe -r ath10k_pci
>>>      $ sudo modprobe -r ath10k_core
>>>      $ sudo modprobe ath10k_pci
>>>
>>> ```
>>> [   49.441618] ath10k_pci 0000:3a:00.0: wmi service ready event not received
>>> [   49.523814] ath10k_pci 0000:3a:00.0: Could not init core: -110
> 
> [...]
> 
>> Are you using a distro kernel?

The 6.8.11 is Debian’s current Linux kernel in the suite *unstable/sid*
(*linux-image-6.8.11-amd64* 6.8.11-1).

>> Could you check if below patch merged in your kernel? if not can
>> you merge it and try again?
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=e57b7d62a1b2f496caf0beba81cec3c90fad80d5
> 
> Paul, if you are feeling brave to try out an -rc this commit is in just
> released v6.10-rc1.

Thank you. I haven’t found out yet, how to reproduce this. I’ll keep an 
eye on it.

As the commit message says:

> This results in timeout issue if the interrupt is not fired, due to
> some unknown reasons.

There are reports from 2016 to 2021 with similar symptoms. These were 
supposedly fixed with 
`/usr/lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin` [1][2]:

     $ md5sum /usr/lib/firmware/ath10k/QCA6174/hw3.0/board.bin 
/usr/lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
     cb37c63d9ca28f53fea1ff09ad7c7a82 
/usr/lib/firmware/ath10k/QCA6174/hw3.0/board.bin
     651e921b372848b3928621e6f1d34b01 
/usr/lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin


Kind regards,

Paul


[1]: https://github.com/kvalo/ath10k-firmware/pull/2
[2]: https://github.com/linux-surface/linux-surface/issues/41