All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Baochen Qiang <quic_bqiang@quicinc.com>,
	linux-wireless@vger.kernel.org,  ath10k@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	 Hans de Goede <hdegoede@redhat.com>,
	James Prestwood <prestwoj@gmail.com>
Subject: Re: ath10k_pci 0000:3a:00.0: Could not init core: -110
Date: Mon, 27 May 2024 16:42:10 +0300	[thread overview]
Message-ID: <87o78r8j7x.fsf@kernel.org> (raw)
In-Reply-To: <96828117-2cf8-4a34-a8e6-78ace96b32d3@molgen.mpg.de> (Paul Menzel's message of "Mon, 27 May 2024 12:24:59 +0200")

Paul Menzel <pmenzel@molgen.mpg.de> writes:

> 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

Most likely that's a different issue from yours, just with same symptoms
(firmware crashing during firmware initialisation). I have seen also
cases when the firmware crashes when using a wrong board file, but I
suspect your board file is correct.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2024-05-27 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27  8:42 ath10k_pci 0000:3a:00.0: Could not init core: -110 Paul Menzel
2024-05-27  9:00 ` Baochen Qiang
2024-05-27  9:10   ` Kalle Valo
2024-05-27 10:24     ` Paul Menzel
2024-05-27 13:42       ` Kalle Valo [this message]
2024-05-28 11:42       ` James Prestwood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o78r8j7x.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=prestwoj@gmail.com \
    --cc=quic_bqiang@quicinc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.