From nobody Sat Nov 02 16:27:31 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Xgjnr60rMz5cJHg for ; Sat, 02 Nov 2024 16:28:00 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:313::1:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xgjnr1Z6gz4QcB for ; Sat, 2 Nov 2024 16:28:00 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1730564870; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=RLFgx7ylEe8+w2NY9hu4TwY9hUo0LMyBcN1yYSqaQ/A=; b=RbuBPt5c7eBeVJqqOiscdOCMRzma97A/N0Lb6kmPc0puL5kA35vtfoiErJjzjQmEMIE5eo uUDQSCIxjUnDlJVxO7U79cZCohqeCJ3jlB6AYx29VIFZrhis/vFwzoXf9rIcTCamTj1WOO 2prMlZXf0KAoN7hfg3I4UiEoQuYqozQOi8ppLIspWzIH2TNDpvMdR2R/QNelHJeUyLH8Ry wuCkEtXQPQhZnLKctUSISVlomJcDrT7yAJ1pEceV2Y1XHQpa4q+oEcbluYEywT5InW+6p7 rLzFs4swDuaZi+w13Eq1H4XdxvictB3OuYg7a+fFPYnbo2aMrQFjM403Hp/3bg== Date: Sat, 02 Nov 2024 17:27:31 +0100 From: Alexander Leidinger To: Warner Losh Cc: Current FreeBSD Subject: Re: No valid device tree blob found! In-Reply-To: References: <8cf9adb0e7ca6340460c695ffd64a0df@Leidinger.net> <896b9ce404ffcb126dcdd6008583b117@Leidinger.net> Message-ID: Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_c425043fe93d42fdda401d2b2c3ec2c8"; micalg=pgp-sha256 X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:2a00:1828::/32, country:DE] X-Rspamd-Queue-Id: 4Xgjnr1Z6gz4QcB X-Spamd-Bar: ---- This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_c425043fe93d42fdda401d2b2c3ec2c8 Content-Type: multipart/alternative; boundary="=_9608a4048bb4aead6aae6bc5feb75b5b" --=_9608a4048bb4aead6aae6bc5feb75b5b Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8; format=flowed Am 2024-11-02 17:08, schrieb Warner Losh: > On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger > 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? If I re-apply all local stuff (including the config) each time. What I don't like about bisect is it loses all local changes of a merge during bisecting. I have build and install scripts and the kernel config in the repo... Any tips&tricks to not lose the merged changes and hand-applying them during a bisect (I prefer to keep the scripts inside the repo which they apply to)? Tedious bisect in progress... Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_9608a4048bb4aead6aae6bc5feb75b5b Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

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



On Sat, Nov 2, 2024, 10:03=E2=80=AF= AM Alexander Leidinger <Alexander@leidinger.net> wrote:
Am 2024-10-30 22:11, schrieb Alexand= er Leidinger:

> WARNING! Trying to fire up the kernel, but no= device tree blob found!

For anyone interested, I opened
<= a href=3D"https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282493" targe= t=3D"_blank" rel=3D"noopener noreferrer">https://bugs.freebsd.org/bugzilla/= show_bug.cgi?id=3D282493 for this.
 
Yea. This is a hang or a bad console. The warning is lame= and misleading.
 
Can you bisect?

If I re-apply all local stuff (including the config) each time. What I d= on't like about bisect is it loses all local changes of a merge during bise= cting. I have build and install scripts and the kernel config in the repo..= =2E

Any tips&tricks to not lose the merged changes and hand-applying the= m during a bisect (I prefer to keep the scripts inside the repo which they = apply to)?

Tedious bisect in progress...

Bye,
Alexander.

--
= http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http:/= /www.FreeBSD.org    n= etchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF
--=_9608a4048bb4aead6aae6bc5feb75b5b-- --=_c425043fe93d42fdda401d2b2c3ec2c8 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmcmUwMACgkQEg2wmwP4 2IatcBAAlnfhY3c2yPoTqFyE0d91jUJF6UIIMXc1ol3slNOS0FlAQkig/W06Bm1O He8uHixEe2ckWK7XrkGodN+yEbE+95eAK41kz0PHz9u8jrgDFqi2YBB4cCxc9ADx LJ56FRvga9vU5OZNBymagVzkyEIFOalke/A1RXwEZQX6oFdZ+jVYBnoY57hkeciA fefnLK6OlVhrUq6Pi7wmGRQGw9s6lfnZ0xPLBM4h4AwebNL37zeA+JFdQYiB9J2B fomKoYNVYqE4lo8+LUQngFBF7LYP4aqG2dOfmAA9rM8JtEPlpmFIqSR2N7DSXUAi BjBsWKO1ZU/+TPMb0XCZufKPbGOt/rF9cMQBIYJWjuXkeucx/den6coe3XCsRYnU oBdNqjgE6i1lEd6r40BS87mWZ8i2J0JxOkABcHYFChGCg3enOr245JwR7ZU0HU/v fYR4BU+CGGH6Ovl0oWvlnQnTdX0YgTIP0oPCgI8vjqfEXGkxFqnVkAc4Y3DIBI7i TlSqGHeSl3OHvli074jVCLr2QVwPSfpFSc15K5hpdzFCUcmDfl3e0kivAl5pBK7H 5Zv7D0jUpC737SPqY8X4YxrKa6U2EhS38Xt1k+LhJsmvCsi8CkYMtNFwzICIHvFX wzJ/apDbB7+zKT0Ey6Kn2zkbCxxOmxqTl1VAvzgk73K8TKQMoqQ= =2wOk -----END PGP SIGNATURE----- --=_c425043fe93d42fdda401d2b2c3ec2c8--