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] [thread-next>] [day] [month] [year] [list]
Message-ID: <78eb0efb-bbaf-4cba-840a-9aa507798075@gmail.com>
Date: Fri, 6 Dec 2024 23:18:36 +0200 (GMT+02:00)
From: Yurii Strilets <yurastr100@...il.com>
To: Armin Wolf <W_Armin@....de>
Cc: platform-driver-x86@...r.kernel.org, regressions@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: [REGRESSION][BISECTED] asus-wmi driver fails on my laptop

Thank you very much for the fix!
I am terribly sorry about a faulty report, I did just find out I had an issue during the mainline build.

Dec 6, 2024 20:15:05 Armin Wolf <W_Armin@....de>:

> Am 06.12.24 um 14:33 schrieb Yura Strilets:
> 
>> Hello,
>> 
>> After upgrading from 6.11 to 6.12 a bunch of Fn+Fx buttons(touchpad,
>> mic, kb backlight, my asus) stopped working and the
>> /sys/(...)/asus::kbd_backlight interface is missing, which,
>> considering the dmesg, looks like an asus-wmi driver issue.
>> 
>> I've been able to bisect the issue to the commit
>> [b012170fed282151f7ba8988a347670c299f5ab3] "platform/x86: asus-wmi:
>> Fix thermal profile initialization"
>> 
>> Additionally, here's some maybe-helpful information:
>> my laptop's model -- ASUS Zenbook UX3402VA
>> linux distro -- Arch Linux
>> .config for bisection -- was taken from /proc/config.gz at 6.12.1 arch
>> kernel(attached in [1]) and missing options are default
>> dmesg logs -- The "grep asus" parts of both good and bad scenarios can
>> be seen below and full logs are at [2] and [3]
>> 
>> == bad.log ==
>> [    3.664546] asus_wmi: ASUS WMI generic driver loaded
>> [    3.713358] asus_wmi: Initialization: 0x1
>> [    3.714126] asus_wmi: SFUN value: 0x21
>> [    3.714131] asus-nb-wmi asus-nb-wmi: Detected ATK, not ASUSWMI, use
>> DSTS
>> [    3.757420] asus_wmi: Failed to set throttle thermal policy
>> (retval): 0x0
>> [    3.757425] asus_wmi: Failed to set default thermal profile
>> [    3.757429] asus-nb-wmi asus-nb-wmi: probe with driver asus-nb-wmi
>> failed with error -5
>> == end ==
>> 
>> == good.log ==
>> [    4.557898] asus_wmi: ASUS WMI generic driver loaded
>> [    4.776587] asus_wmi: Initialization: 0x1
>> [    4.777253] asus_wmi: SFUN value: 0x21
>> [    4.777256] asus-nb-wmi asus-nb-wmi: Detected ATK, not ASUSWMI, use
>> DSTS
>> [    4.777258] asus-nb-wmi asus-nb-wmi: Detected ATK, enable event queue
>> [    4.805497] input: Asus WMI hotkeys as
>> /devices/platform/asus-nb-wmi/input/input15
>> == end ==
>> 
>> [1] .config - https://pastebin.com/raw/3nDSV8Sm
>> [2] bad.log - https://pastebin.com/raw/fvR5Sjzt
>> [3] good.log - https://pastebin.com/raw/EazfLAWA
>> 
>> Thanks,
>> Yurii
>> 
> I am aware of this issue, the necessary fix (commit 25fb5f47f34d) was already submitted upstream and will likely
> show up in the stable kernels soon.
> 
> Thanks,
> Armin Wolf

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ