linux-kernel - Re: Atheros QCA6174 ath10k

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: <cafad11a-d7c7-4b68-880a-d6e05578fa5c@gmail.com>
Date:   Mon, 25 Sep 2023 17:15:20 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Kalle Valo <kvalo@...nel.org>
Cc:     Cool Goose <coolgoose54@...oo.in>,
        Linux ath10k <ath10k@...ts.infradead.org>,
        Jeff Johnson <quic_jjohnson@...cinc.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Atheros QCA6174 ath10k_pci fimware crashing

On 25/09/2023 17:08, Kalle Valo wrote:
> Bagas Sanjaya <bagasdotme@...il.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