From: Romain Naour <romain.naour@smile.fr>
To: Tony Lindgren <tony@atomide.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: Nishanth Menon <nm@ti.com>, Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: Unable to boot 6.0-rc3 on dra76
Date: Tue, 6 Sep 2022 09:24:32 +0200 [thread overview]
Message-ID: <79d045ca-38ac-7ad2-3944-e980f0cff0ed@smile.fr> (raw)
In-Reply-To: <Yxbd3xbv2elWZ6/I@atomide.com>
Hello,
Le 06/09/2022 à 07:42, Tony Lindgren a écrit :
> * Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> [220831 12:22]:
>> On 31/08/2022 14:54, Tony Lindgren wrote:
>>> * Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> [220831 11:35]:
>>>> Hi,
>>>>
>>>> I've been unable to boot 6.0-rc3 on dra76 evm with omap2plus_defconfig. I get no output from the kernel.
>>>> Enabling earlyprintk gives me the following. Any ideas?
>>>
>>> This series of fixes for deferred probe in Linux next should help:
>>>
>>> https://lore.kernel.org/linux-kernel/20220819221616.2107893-1-saravanak@google.com/
>>>
>>> Hopefully it will get merged to the mainline kernel soonish.
>>
>> Thanks Tony! This solves the issue.
>
> Looks like the deferred probe fixes are now merged in v6.0-rc4 FYI.
Just to let you know, I had the same boot issue with the kernel v6.0-rc2 and I
reverted locally the series removing the driver_deferred_probe_check_state().
I'm using an AM5749 cpu on a custom board.
I'm glad to see the problem fixed for v6.0-rc4.
Best regards,
Romain
>
> Tony
next prev parent reply other threads:[~2022-09-06 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 11:42 Unable to boot 6.0-rc3 on dra76 Tomi Valkeinen
2022-08-31 11:54 ` Tony Lindgren
2022-08-31 12:30 ` Tomi Valkeinen
2022-09-06 5:42 ` Tony Lindgren
2022-09-06 7:24 ` Romain Naour [this message]
2022-09-06 7:40 ` Tony Lindgren
2022-09-06 12:14 ` Romain Naour
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=79d045ca-38ac-7ad2-3944-e980f0cff0ed@smile.fr \
--to=romain.naour@smile.fr \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tony@atomide.com \
/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