regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Pierre Asselin" <pa@panix.com>
To: "\"Uwe Kleine-König\"" <u.kleine-koenig@pengutronix.de>
Cc: "Pierre Asselin" <pa@panix.com>,
	linux-acpi@vger.kernel.org, regressions@lists.linux.dev,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [Regression] acpi: laptop panics early in boot
Date: Tue, 7 Mar 2023 14:31:49 -0500	[thread overview]
Message-ID: <6d97df76de719871c90fb59726f2d6b0.squirrel@mail.panix.com> (raw)
In-Reply-To: <20230307161005.6m6fpi3oxa3jn2wg@pengutronix.de>

> Maybe the following patch helps (on top of v6.3-rc1):
>
> diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
> index 9531dd0fef50..a5a8f82981ce 100644
> --- a/drivers/acpi/bus.c
> +++ b/drivers/acpi/bus.c
> @@ -518,7 +518,7 @@ static void acpi_bus_notify(acpi_handle handle, u32
> type, void *data)
>  	if (!adev)
>  		goto err;
>
> -	if (adev->dev.driver) {
> +	if (device_is_bound(&adev->dev)) {
>  		struct acpi_driver *driver = to_acpi_driver(adev->dev.driver);
>
>  		if (driver && driver->ops.notify &&
>

It does indeed "fix" 6.3-rc1.  Modulo locking issues, which I am
not qualified to evaluate.



  reply	other threads:[~2023-03-07 19:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 21:45 [Regression] acpi: laptop panics early in boot Pierre Asselin
2023-03-07  9:33 ` Uwe Kleine-König
2023-03-07 14:25   ` Pierre Asselin
2023-03-07 16:10     ` Uwe Kleine-König
2023-03-07 19:31       ` Pierre Asselin [this message]
2023-03-23 12:31         ` Linux regression tracking (Thorsten Leemhuis)
2023-03-23 13:16           ` Uwe Kleine-König
2023-03-23 17:20             ` Pierre Asselin
     [not found]         ` <20230307200843.yxhvnb23tpecjjng@pengutronix.de>
2023-03-23 21:22           ` Uwe Kleine-König
2023-03-24 12:12             ` Rafael J. Wysocki
2023-03-24 12:27               ` Uwe Kleine-König
2023-03-24 15:02             ` Pierre Asselin
2023-03-24 11:54           ` Rafael J. Wysocki
2023-04-17 11:41 ` Linux regression tracking #update (Thorsten Leemhuis)

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=6d97df76de719871c90fb59726f2d6b0.squirrel@mail.panix.com \
    --to=pa@panix.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).