On 9/3/22 08:13, Eugene Shalygin wrote:
Guenter,
yes, there is a patch that I don't really understand, but it fixes a
very similar problem:
https://bugzilla.kernel.org/show_bug.cgi?id=216412 I will test today
that change with a hardware where it needs to autoload and submit the
patch if it works.
I don't understand why that works either. Maybe it interferes with other
PNP0C09 devices and/or the code in drivers/acpi/ec.c.
Couple of comments:
- You'll need to drop __init.
- No need or reason to rename asus_ec_sensors_platform_driver
to asus_ec_sensors_platform_driver_probe.
Thanks,
Guenter
Best regards,
Eugene
On Sat, 3 Sept 2022 at 17:09, Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
On 9/3/22 04:00, Christopher Klooz wrote:
Hi Eugene,
Currently, we have user reports of at least 4 Fedora installations that have issues with asus_ec_sensors since 5.19.4. They remain in 5.19.6.
All issues can be solved by blacklisting asus_ec_sensors.
https://bugzilla.redhat.com/show_bug.cgi?id=2121844
The bugzilla report contains kernel logs of two machines, one with nvidia-driver and one without a tainted kernel.
The report and the contained ask.fedora link contain some elaborations of how the issue manifests at the users' machines. The major issue is a wrong output of battery power percentage (in one case it gets stuck, in the other cases is becomes erratic). Also, in one case it has effects on suspending (see the report).
On the Internet, there are already reports from other Linux distributions noting the issue and the same solution (blacklisting).
Eugene,
do you have an immediate idea other than reverting the patch pointed to in the bug report ?
Thanks,
Guenter
