All of
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
Subject: Re: Issue in asus_ec_sensors in Fedora installations and other distributions #forregzbot
Date: Sun, 4 Sep 2022 11:33:24 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

[TLDR: I'm adding this regression report to the list of tracked
regressions; all text from me you find below is based on a few templates
paragraphs you might have encountered already already in similar form.]

Hi, this is your Linux kernel regression tracker.

On 03.09.22 13: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).
> Thanks for maintaining & regards,

Thanks for the report. To be sure below issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
tracking bot:

#regzbot introduced 5cd29012028d ^
#regzbot title asus_ec_sensors: causes misbehaviour; likely dup of
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:

Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (the mail this one replies to), as explained for
in the Linux kernel's documentation; above webpage explains why this is
important for tracked regressions.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

  parent reply	other threads:[~2022-09-04  9:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
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   ` Thorsten Leemhuis [this message]
2022-09-06 20:10   ` Guenter Roeck
2022-09-06 20:23     ` 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:

* 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.