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

Date: Tue, 28 May 2024 04:42:29 -0700
From: James Prestwood <prestwoj@...il.com>
To: Paul Menzel <pmenzel@...gen.mpg.de>, 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>
Subject: Re: ath10k_pci 0000:3a:00.0: Could not init core: -110

Hi Paul,

> Thank you. I haven’t found out yet, how to reproduce this. I’ll keep 
> an eye on it.
>
This seems like the original bug I reported here:

https://lore.kernel.org/linux-wireless/304ce305-fbe6-420e-ac2a-d61ae5e6ca1a@gmail.com/

Note its not specific to power save which I originally thought, but you 
can reproduce it somewhat easily (at least I could) by simply 
adding/removing the wlan interface in a loop. IIRC even just ifup/ifdown 
would eventually trigger it.

But so far the patch Baochen submitted completely resolved the problem.

Thanks,

James