From: Guenter Roeck <firstname.lastname@example.org>
To: Eugene Shalygin <email@example.com>
Cc: Christopher Klooz <firstname.lastname@example.org>,
Subject: Re: Issue in asus_ec_sensors in Fedora installations and other distributions
Date: Sat, 3 Sep 2022 08:42:33 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
On 9/3/22 08:13, Eugene Shalygin wrote:
> 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
> Best regards,
> On Sat, 3 Sept 2022 at 17:09, Guenter Roeck <firstname.lastname@example.org> 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.
>>> 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).
>> do you have an immediate idea other than reverting the patch pointed to in the bug report ?
next prev parent reply other threads:[~2022-09-03 15:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
2022-09-03 11:00 ` Issue in asus_ec_sensors in Fedora installations and other distributions Christopher Klooz
2022-09-03 15:09 ` Guenter Roeck
2022-09-03 15:13 ` Eugene Shalygin
2022-09-03 15:42 ` Guenter Roeck [this message]
2022-09-03 19:40 ` Eugene Shalygin
2022-09-03 22:00 ` Guenter Roeck
2022-09-03 22:37 ` Eugene Shalygin
2022-09-03 23:47 ` Guenter Roeck
2022-09-04 13:19 ` Eugene Shalygin
2022-09-04 14:10 ` Guenter Roeck
2022-09-03 15:48 ` Christopher Klooz
2022-09-04 9:33 ` Issue in asus_ec_sensors in Fedora installations and other distributions #forregzbot Thorsten Leemhuis
2022-09-06 20:10 ` Issue in asus_ec_sensors in Fedora installations and other distributions Guenter Roeck
2022-09-06 20:23 ` Eugene Shalygin
2022-09-15 8:25 ` Guenter Roeck
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.