linux-kernel - Re: qca6174 hw3.2 target 0x05030000 chip

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

Message-ID: <12cc81d5-f134-4460-9139-754a69821f12@molgen.mpg.de>
Date: Wed, 14 May 2025 10:23:44 +0200
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Jamie <jamie@...mulussoft.com>
Cc: Baochen Qiang <quic_bqiang@...cinc.com>,
 Jeff Johnson <jjohnson@...nel.org>, ath10k@...ts.infradead.org,
 LKML <linux-kernel@...r.kernel.org>
Subject: Re: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff: firmware
 crashed!

Dear Jamie,

Am 14.05.25 um 10:19 schrieb Jamie:
> Check your voltages. In my case, my voltage settings were wrong.

Where did you do this? In the system firmware?

> After adjusting them, the drivers started working again.
Then it’s a different problem. I am using a Dell XPS 13 9360 laptop, and 
I didn’t fiddle with any voltages. Even if Linux’ power management 
behavior changed, it’s hard to pinpoint a possible regression, as I have 
no reproducer.

Kind regards,

Paul