From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Hans de Goede <hdegoede@redhat.com>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: ACPI scan regression -> Boot fail on Cherrytrail w/ 5.11-rc3
Date: Fri, 15 Jan 2021 08:52:52 -0600 [thread overview]
Message-ID: <b56e75b7-2cdb-dd82-e9eb-f05414b8a970@linux.intel.com> (raw)
In-Reply-To: <2473340.5W3TeCB90J@kreacher>
>> Yep, those 'hacks' solve the boot problem on my device. I tried multiple
>> times and it's completely reproducible.
>>
>>> And can you collect an acpidump from the device and either send it to me and Rafael
>>> offlist, or upload it somewhere and send us a link ?
>>
>> will do
>
> In addition to what Hans asked for, can you please build the kernel with the
> debug patch below applied (instead of the Hans' debug patch), try to boot
> the affected machine with it and see what is missing with respect to booting
> the kernel with the two problematic commits reverted?
Sorry, not following. Are you asking me to apply the patch below as well
as revert the two problematic commits? Or just the patch below? the boot
process is stuck without the reverts and I don't have a serial link to
see what happens (closed form-factor).
> Also please send me the outout of "dmesg | grep "Enumeration" from the debug
> kernel if possible. >
> ---
> drivers/acpi/scan.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-pm/drivers/acpi/scan.c
> ===================================================================
> --- linux-pm.orig/drivers/acpi/scan.c
> +++ linux-pm/drivers/acpi/scan.c
> @@ -1951,7 +1951,7 @@ static acpi_status acpi_bus_check_add(ac
> u32 count = acpi_scan_check_dep(handle);
> /* Bail out if the number of recorded dependencies is not 0. */
> if (count > 0) {
> - acpi_bus_scan_second_pass = true;
> + acpi_handle_info(handle, "Enumeration skipped\n");
> return AE_CTRL_DEPTH;
> }
> }
>
>
>
next prev parent reply other threads:[~2021-01-15 14:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 21:55 ACPI scan regression -> Boot fail on Cherrytrail w/ 5.11-rc3 Pierre-Louis Bossart
2021-01-14 23:34 ` Hans de Goede
2021-01-15 0:49 ` Pierre-Louis Bossart
2021-01-15 8:54 ` Hans de Goede
2021-01-15 13:38 ` Rafael J. Wysocki
2021-01-15 13:54 ` Rafael J. Wysocki
2021-01-15 14:52 ` Pierre-Louis Bossart [this message]
2021-01-15 14:55 ` Rafael J. Wysocki
2021-01-15 15:09 ` Pierre-Louis Bossart
2021-01-15 15:22 ` Rafael J. Wysocki
2021-01-15 15:38 ` Pierre-Louis Bossart
2021-01-15 16:05 ` Hans de Goede
2021-01-15 16:22 ` Rafael J. Wysocki
2021-01-15 16:41 ` Pierre-Louis Bossart
2021-01-15 19:01 ` Rafael J. Wysocki
2021-01-15 19:06 ` Rafael J. Wysocki
2021-01-15 20:48 ` Hans de Goede
2021-01-15 21:57 ` Hans de Goede
[not found] ` <56b732f4-9a24-688e-7cc7-6c2522d173c9@linux.intel.com>
2021-01-16 11:18 ` Hans de Goede
2021-01-16 12:26 ` Hans de Goede
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=b56e75b7-2cdb-dd82-e9eb-f05414b8a970@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.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