From: Guenter Roeck <linux@roeck-us.net>
To: Christopher Klooz <py0xc3@my.mail.de>
Cc: eugene.shalygin@gmail.com, linux-hwmon@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: Issue in asus_ec_sensors in Fedora installations and other distributions
Date: Tue, 6 Sep 2022 13:10:35 -0700 [thread overview]
Message-ID: <20220906201035.GA3453623@roeck-us.net> (raw)
In-Reply-To: <47e41e8f-f6b2-4bc7-de3f-0c811ee6fdf7@my.mail.de>
On Sat, Sep 03, 2022 at 01:00:33PM +0200, 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).
>
> Thanks for maintaining & regards,
>
Are we getting any closer to fixing this problem ? If not, I'll have to start
reverting patches or even declare the driver as BROKEN.
Thanks,
Guenter
next prev parent reply other threads:[~2022-09-06 20:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6026b5e2-a8f5-1058-6112-f191bde333a6@my.mail.de>
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
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 ` Guenter Roeck [this message]
2022-09-06 20:23 ` Issue in asus_ec_sensors in Fedora installations and other distributions Eugene Shalygin
2022-09-15 8:25 ` Guenter Roeck
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220906201035.GA3453623@roeck-us.net \
--to=linux@roeck-us.net \
--cc=eugene.shalygin@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=py0xc3@my.mail.de \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).