From: Pavel Machek <pavel@ucw.cz>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Len Brown <len.brown@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Kevin Hilman <khilman@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: boot stuck at starting kernel, due to __genpd_dev_pm_attach?
Date: Mon, 15 Aug 2022 20:23:07 +0200 [thread overview]
Message-ID: <20220815182307.GA4658@duo.ucw.cz> (raw)
In-Reply-To: <Yvpd2pwUJGp7R+YE@euler>
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
Hi!
> You might have already gotten this report, but I tried running v6.0-rc1
> on my BeagleBone Black and it gets stuck right after "Starting kernel
> ..." from U-Boot.
>
> A bisect pointed me to commit 5a46079a9645 ("PM: domains: Delete usage
> of driver_deferred_probe_check_state()").
>
> I don't have much more detail than that, other than I'm using the
> in-tree am335x-boneblack.dts device tree and I believe I had tested with
> the multi-v7-defconfig for this verification. I'm happy to test anything
> that might offer more information.
Well, standart next step is reverting 5a46079a9645 on top of v6.0-rc1,
and if it starts working, either you get fix in your inbox, or you ask
Linus to revert :-).
Best regards,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-08-15 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 14:53 boot stuck at starting kernel, due to __genpd_dev_pm_attach? Colin Foster
2022-08-15 18:23 ` Pavel Machek [this message]
2022-08-16 0:27 ` Colin Foster
2022-08-16 0:43 ` Saravana Kannan
2022-08-17 5:48 ` Colin Foster
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=20220815182307.GA4658@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=colin.foster@in-advantage.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
--cc=ulf.hansson@linaro.org \
/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