From: Guenter Roeck <linux@roeck-us.net>
To: Eugene Shalygin <eugene.shalygin@gmail.com>
Cc: Christopher Klooz <py0xc3@my.mail.de>,
linux-hwmon@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Issue in asus_ec_sensors in Fedora installations and other distributions
Date: Thu, 15 Sep 2022 01:25:11 -0700 [thread overview]
Message-ID: <20220915082511.GA1313949@roeck-us.net> (raw)
In-Reply-To: <CAB95QAQRT5p5k=0D781aOra9uF3vw-92+T_CePd_7tzJDDH0Yg@mail.gmail.com>
On Tue, Sep 06, 2022 at 10:23:08PM +0200, Eugene Shalygin wrote:
> On Tue, 6 Sept 2022 at 22:10, Guenter Roeck <linux@roeck-us.net> wrote:
> > 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.
>
> Out of a few workarounds I've tried, none worked. I rework the module
> autoloading back to plain dmi data. Sorry, I'm totally busy until this
> Friday and can't prepare a patch until the end of the week. If that is
> too late, removing just the module autoloading
> (MODULE_DEVICE_TABLE(acpi, ...)) will fix the problem.
>
Let's see if this works:
#regzbot fixed-by: 88700d1396ba
Guenter
prev parent reply other threads:[~2022-09-15 8:50 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 ` 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 [this message]
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=20220915082511.GA1313949@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).