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>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-acpi@vger.kernel.org, regressions@lists.linux.dev,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"\"Robert Święcki\"" <robert@swiecki.net>
Subject: Re: [Regression] acpi: laptop panics early in boot
Date: Fri, 24 Mar 2023 11:02:13 -0400	[thread overview]
Message-ID: <8ac89f507c8e5c14635d215284f2f2b1.squirrel@mail.panix.com> (raw)
In-Reply-To: <20230323212212.udho2htrhd2vlzxm@pengutronix.de>

> This mail didn't make it into the archive on lore.kernel.org. Did
> someone receive it? If not, that would explain why I didn't get any
> feedback on it ...

First time I see it.

>> diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
>> index 9531dd0fef50..fddca263ac40 100644
>> --- a/drivers/acpi/bus.c
>> +++ b/drivers/acpi/bus.c
>> @@ -518,13 +518,15 @@ static void acpi_bus_notify(acpi_handle handle,
>> u32 type, void *data)
>>  	if (!adev)
>>  		goto err;
>>
>> -	if (adev->dev.driver) {
>> +	device_lock(&adev->dev);
>> +	if (device_is_bound(&adev->dev)) {
>>  		struct acpi_driver *driver = to_acpi_driver(adev->dev.driver);
>>
>>  		if (driver && driver->ops.notify &&
>>  		    (driver->flags & ACPI_DRIVER_ALL_NOTIFY_EVENTS))
>>  			driver->ops.notify(adev, type);
>>  	}
>> +	device_unlock(&adev->dev);
>>
>>  	if (!hotplug_event) {
>>  		acpi_put_acpi_dev(adev);
>>

This patch works, in that the kernel reaches early userspace reliably.
I would want to test it more extensively, i.e. install the modules and
run it for real instead of just kexec-ing the bzImage.  I'll test Rafael's
patch first.

Full disclosure: I made small changes to the starting .config, see below.
6.3-rc1 is still bad with the new .config, the patch makes it good.
The changes:
  1) PROVE_LOCKING=y
  2) CONFIG_DEBUG_ATOMIC_SLEEP=y  (why not, what could go wrong :)
  3) radeon driver modular instead of built-in.
I don't think it matters.  Here is the diffconfig, just in case.

-EXTRA_FIRMWARE_DIR "/lib/firmware"
 CEC_CORE y -> m
 DEBUG_ATOMIC_SLEEP n -> y
 DEBUG_LOCK_ALLOC n -> y
 DEBUG_MUTEXES n -> y
 DEBUG_RT_MUTEXES n -> y
 DEBUG_RWSEMS n -> y
 DEBUG_SPINLOCK n -> y
 DEBUG_WW_MUTEX_SLOWPATH n -> y
 DRM_DISPLAY_HELPER y -> m
 DRM_KMS_HELPER y -> m
 DRM_RADEON y -> m
 DRM_TTM y -> m
 DRM_TTM_HELPER y -> m
 EXTRA_FIRMWARE "radeon/R300_cp.bin" -> ""
 FB_CFB_COPYAREA y -> m
 FB_CFB_FILLRECT y -> m
 FB_CFB_IMAGEBLIT y -> m
 FB_SYS_COPYAREA y -> m
 FB_SYS_FILLRECT y -> m
 FB_SYS_FOPS y -> m
 FB_SYS_IMAGEBLIT y -> m
 I2C_ALGOBIT y -> m
 PROVE_LOCKING n -> y
+DEBUG_LOCKDEP n
+LOCKDEP y
+LOCKDEP_BITS 15
+LOCKDEP_CHAINS_BITS 16
+LOCKDEP_CIRCULAR_QUEUE_BITS 12
+LOCKDEP_STACK_TRACE_BITS 19
+LOCKDEP_STACK_TRACE_HASH_BITS 14
+PREEMPTIRQ_TRACEPOINTS y
+PROVE_RAW_LOCK_NESTING n
+PROVE_RCU y
+TRACE_IRQFLAGS y
+TRACE_IRQFLAGS_NMI y



  parent reply	other threads:[~2023-03-24 15:02 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
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 [this message]
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=8ac89f507c8e5c14635d215284f2f2b1.squirrel@mail.panix.com \
    --to=pa@panix.com \
    --cc=bhelgaas@google.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=robert@swiecki.net \
    --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).