linux-kernel - Re: [PATCH 1/1] wifi: ath11k: pcic: make memory access more readable

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]

Message-ID: <5bd6c864-018b-4401-8c1b-7bad023de75b@oss.qualcomm.com>
Date: Wed, 5 Mar 2025 09:42:05 -0800
From: Jeff Johnson <jeff.johnson@....qualcomm.com>
To: Ziyang Huang <hzyitc@...look.com>, Steev Klimaszewski <steev@...i.org>
Cc: ath11k@...ts.infradead.org, jjohnson@...nel.org, johannes@...solutions.net,
        linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: [PATCH 1/1] wifi: ath11k: pcic: make memory access more readable

On 3/5/2025 6:41 AM, Ziyang Huang wrote:
> 在 2025/3/4 14:33, Steev Klimaszewski 写道:
>> Hi Ziyang,
>>
>> With this patch applied, on the Thinkpad X13s which has an ath11k, I am seeing
>> the following:
>>
>>   ath11k_pci 0006:01:00.0: chip_id 0x2 chip_family 0xb board_id 0x8c soc_id 0x400c0210
>>   ath11k_pci 0006:01:00.0: fw_version 0x11088c35 fw_build_timestamp 2024-04-17 08:34 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41
>>   ath11k_pci 0006:01:00.0: firmware crashed: MHI_CB_EE_RDDM
>>   ath11k_pci 0006:01:00.0: ignore reset dev flags 0xc800
>>   ath11k_pci 0006:01:00.0: failed to receive control response completion, polling..
>>   ath11k_pci 0006:01:00.0: ctl_resp never came in (-110)
>>   ath11k_pci 0006:01:00.0: failed to connect to HTC: -110
>>   ath11k_pci 0006:01:00.0: failed to start core: -110
>>   failed to send QMI message
>>   ath11k_pci 0006:01:00.0: failed to send wlan mode request (mode 4): -5
>>   ath11k_pci 0006:01:00.0: qmi failed to send wlan mode off: -5
>>
>> I'm pretty sure this isn't supposed to happen?
>>
>> --steev
> 
> Oh, give me some time to check what happen.

I suggest you not spend time on this unless you can test this on all hardware
supported by ath11k.

/jeff