From: "Toralf Förster" <toralf.foerster@gmx.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Randy Dunlap <rdunlap@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: regression 5.6.4->5.6.5 at drivers/acpi/ec.c
Date: Fri, 17 Apr 2020 21:41:30 +0200 [thread overview]
Message-ID: <d66ad8f1-d7c5-dd8a-0eb4-9e560dc9ada1@gmx.de> (raw)
In-Reply-To: <CAJZ5v0icdVL6_yGpfsorqszdi9GcLxzYdvDqTJyG4ENzkOG2pQ@mail.gmail.com>
On 4/17/20 8:52 PM, Rafael J. Wysocki wrote:
> On Fri, Apr 17, 2020 at 6:36 PM Toralf Förster <toralf.foerster@gmx.de> wrote:
>>
>> On 4/17/20 5:53 PM, Rafael J. Wysocki wrote:
>>> Does the patch below (untested) make any difference?
>>>
>>> ---
>>> drivers/acpi/ec.c | 5 ++++-
>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>>
>>> Index: linux-pm/drivers/acpi/ec.c
>>> ===================================================================
>>> --- linux-pm.orig/drivers/acpi/ec.c
>>> +++ linux-pm/drivers/acpi/ec.c
>>> @@ -2067,7 +2067,10 @@ static struct acpi_driver acpi_ec_driver
>>> .add = acpi_ec_add,
>>> .remove = acpi_ec_remove,
>>> },
>>> - .drv.pm = &acpi_ec_pm,
>>> + .drv = {
>>> + .probe_type = PROBE_FORCE_SYNCHRONOUS,
>>> + .pm = &acpi_ec_pm,
>>> + },
>>> };
>>>
>>> static void acpi_ec_destroy_workqueues(void)
>> I'd say no, but for completeness:
>
> OK, it looks like mainline commit
>
> 65a691f5f8f0 ("ACPI: EC: Do not clear boot_ec_is_ecdt in acpi_ec_add()")
>
> was backported into 5.6.5 by mistake.
>
> Can you please revert that patch and retest?
>
Yes, reverting that commit solved the issue.
--
Toralf
next prev parent reply other threads:[~2020-04-17 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 15:10 Toralf Förster
2020-04-17 15:17 ` Randy Dunlap
2020-04-17 15:53 ` Rafael J. Wysocki
2020-04-17 16:36 ` Toralf Förster
2020-04-17 18:52 ` Rafael J. Wysocki
2020-04-17 19:41 ` Toralf Förster [this message]
2020-04-17 19:54 ` Rafael J. Wysocki
2020-04-18 8:09 ` Greg Kroah-Hartman
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=d66ad8f1-d7c5-dd8a-0eb4-9e560dc9ada1@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rjw@rjwysocki.net \
/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
all inboxes | Powered by JetHome®