Re: No valid device tree blob found!

Am 2024-11-02 17:08, schrieb Warner Losh:

> On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger 
> <Alexander@leidinger.net> wrote:
> 
>> Am 2024-10-30 22:11, schrieb Alexander Leidinger:
>> 
>>> WARNING! Trying to fire up the kernel, but no device tree blob found!
>> 
>> For anyone interested, I opened
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282493 for this.
> 
> Yea. This is a hang or a bad console. The warning is lame and 
> misleading.
> 
> Can you bisect?

Found it.

# git bisect bad
c87b3f0006be9ac5813f1ff636f18c9b4a41b08e is the first bad commit
commit c87b3f0006be9ac5813f1ff636f18c9b4a41b08e (HEAD)
Author: Warner Losh <imp@FreeBSD.org>
Date:   Mon Oct 14 15:58:10 2024 -0600

     uart: uart_getenv: check for NULL class last, not first

     This allows one to specify dt:XXXX when the default class isn't 
compiled
     into the kernel. It's not an error to not have a class until we're 
done
     parsing the spec, so defer checking until then.

     Sponsored by:           Netflix
     Reviewed by:            adrian, andrew, markj
     Differential Revision:  https://reviews.freebsd.org/D47078

  sys/dev/uart/uart_subr.c | 14 +++++++-------
  1 file changed, 7 insertions(+), 7 deletions(-)

-current as of today without this change boots just fine on the Ampere 
system in the Oracle cloud.

Bye,
Alexander.

-- 
http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    netchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF