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. > > 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, 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 ^ https://bugzilla.redhat.com/show_bug.cgi?id=2121844 #regzbot title asus_ec_sensors: causes misbehaviour; likely dup of https://bugzilla.kernel.org/show_bug.cgi?id=216412 #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: https://linux-regtracking.leemhuis.info/tracked-regression/ 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.
