From nobody Tue Dec 6 16:17:52 2022 X-Original-To: freebsd-arm@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 4NRQZ53tkZz4k2lw for ; Tue, 6 Dec 2022 16:18:05 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NRQZ46GQRz454Y for ; Tue, 6 Dec 2022 16:18:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=7QgGeucx; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2a00:1450:4864:20::62b) smtp.mailfrom=wlosh@bsdimp.com; dmarc=none Received: by mail-ej1-x62b.google.com with SMTP id qk9so7461927ejc.3 for ; Tue, 06 Dec 2022 08:18:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Tqf2Hopp2k3nm74Mwo/yswfeBYdvzBHGWMp/QqxAU5A=; b=7QgGeucxILP84gc7+e2vaN+ntCmVtWG5nB/3V+oodj6K4dK7PXC6pglUHu2dzYVF46 zXMIZHInEPiBbHVfW4ZLvpRzHllLtR6jM1AfRjJB4D5ykaUohmbCBHKBoCJQ7+hw/JT1 08rXNwhXKX27i91zFJNEH0aKH5+fHfdq6kE2C2SlndKrrJWoZN7lWbLiodO2o7heWr08 O+Z1pZQC5VDt9Kz1OJt+fVS03rIOzkdO+TRZXZkFudHoR/crbYFORAWshugLbVhTWmVQ oRyGZEr0RpzMf+snlm7Fr/OLDM1CRRCQrHYByvhADvN8AiDoSCke9EsfHW1GrTjfsE4k AKcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Tqf2Hopp2k3nm74Mwo/yswfeBYdvzBHGWMp/QqxAU5A=; b=mBqGwNoauhN5euKDp8XSSXZA7JKmOf9zbxY07f1QJXiNyl28JH2EoA+BJ8RY3KigSk w/x8wCYaSw3te6jCT6/nw52uzBysJzIBpr6SQUc64fq5gip0avIlptrB2jptTldzflk4 CdrydqyRY9EEigqHWJQ4T/BZIOJL2Df4NCjo7E/RCikbH44UMFvZlmdtf3wVJfH+Hky+ KBvkHU0F0x6O8iwdl6pvYD/wfk36Z40sJlJ72Q8R6mIOU82ZDFnfR55AypdmTl1qy84M difuIAHGQ5tSbCcppn2zO0KmZdr1MCqNNndysp16/OfXcgFUm6sRDq/DtNFToFqZYEYo wJEA== X-Gm-Message-State: ANoB5pmROWYpAmL5y8KRO7EibDyHRqYx+fT86UtjdLg27TQn+wX2vHkb XCrYzhRTi8kthULGD76PHc4i4p1Djk2ccENedpFpFA== X-Google-Smtp-Source: AA0mqf5vTJjoDCKz2jfX0zfAFubrBXdYRdeaTNt0dnx7tHq+HTO75cC9nl+7aEJ+UAH/oh/MoqQcpBv+hTwr1N5ULUE= X-Received: by 2002:a17:907:98ed:b0:7c0:e7a6:cd2d with SMTP id ke13-20020a17090798ed00b007c0e7a6cd2dmr9328391ejc.317.1670343483394; Tue, 06 Dec 2022 08:18:03 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Tue, 6 Dec 2022 09:17:52 -0700 Message-ID: Subject: Re: Succeeded to boot on Lenovo Yoga C630 To: hiroo.ono+freebsd@gmail.com Cc: Mark Millard , freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="000000000000fb226005ef2b25ef" X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FREEMAIL_TO(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_CC(0.00)[yahoo.com,freebsd.org]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62b:from]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; TO_DN_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TAGGED_RCPT(0.00)[freebsd]; DMARC_NA(0.00)[bsdimp.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4NRQZ46GQRz454Y X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --000000000000fb226005ef2b25ef Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Dec 6, 2022 at 7:59 AM Hiroo Ono (=E5=B0=8F=E9=87=8E=E5=AF=9B=E7=94= =9F) wrote: > Thank you. > > 2022=E5=B9=B412=E6=9C=886=E6=97=A5(=E7=81=AB) 3:49 Mark Millard : > > > The following might be involved in your context. > > > > The following is from a successful boot of a HoneyComb via > > UEFI/ACPI (not device tree) via an old log file that I > > have around. Note the first two lines. > > > > . . . > > No valid device tree blob found! > > WARNING! Trying to fire up the kernel, but no device tree blob found! > > EFI framebuffer information: > > addr, size 0x0, 0x0 > > dimensions 0 x 0 > > stride 0 > > masks 0x00000000, 0x00000000, 0x00000000, 0x00000000 > > ---<>--- > > GDB: no debug ports present > > KDB: debugger backends: ddb > > OK, I (and the subject) was wrong. The loader boots, and show > following log at last: > > Loading kernel... > /boot/kernel/kernel text=3D0x2a8 text=3D0x8bcbf0 text=3D0x1f97ac > data=3D0x1a6ac0 data=3D0x0+0x381000 syms=3D[0x8+0x11f6a0+0x8+0x1439ea] > Loading configured modules... > can't find '/boot/entropy' > can't find '/etc/hostid' > No valid device tree blob found! > WARNING! Trying to fire up the kernel, but no device tree blob found! > EFI framebuffer information > addr, size 0x80400000, 0x7e9000 > dimensions 1920 x 1080 > stride 1920 > masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 > > and it stops here. No "<>" line is displayed. > So, it seems that the kernel is loaded but could not be started. There are several causes of this. Most likely is that the console is setup to go somewhere else. Though if you are on the video display and getting that framebuffer output, it won't not go there w/o some setting to override (say to force serial). Next most likely is that FreeBSD doesn't cope well with having both FDT and ACPI information available. But since not DTB is being passed in (per that message) that's not likely at play here. Finally, the loader passes a large number of tables, etc to the kernel. It's quite possible that, for reasons still unknown, that data is wrong or if standard conforming not expected by the kernel. this leads to a crash before we've setup the console in the kernel which looks a lot like a hang. Warner > > . . . > > > > Such also happens for stable/13, releng/13.* based installations > > as well --and likely others too. > > > > ACPI booting does not use Device Tree information but the messages > > are output anyway about the lack. Only if you know that the context > > is a Device Tree style of boot are the messages actually reporting > > a problem. > > > > > > =3D=3D=3D > > Mark Millard > > marklmi at yahoo.com > > > > --000000000000fb226005ef2b25ef Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Dec 6, 2022 at 7:59 AM Hiroo = Ono (=E5=B0=8F=E9=87=8E=E5=AF=9B=E7=94=9F) <hiroo.ono+freebsd@gmail.com> wrote:
Thank you.

2022=E5=B9=B412=E6=9C=886=E6=97=A5(=E7=81=AB) 3:49 Mark Millard <marklmi@yahoo.com>:<= br>
> The following might be involved in your context.
>
> The following is from a successful boot of a HoneyComb via
> UEFI/ACPI (not device tree) via an old log file that I
> have around. Note the first two lines.
>
> . . .
> No valid device tree blob found!
> WARNING! Trying to fire up the kernel, but no device tree blob found!<= br> > EFI framebuffer information:
> addr, size=C2=A0 =C2=A0 =C2=A00x0, 0x0
> dimensions=C2=A0 =C2=A0 =C2=A00 x 0
> stride=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
> masks=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00000000, 0x00000000, 0x0000= 0000, 0x00000000
> ---<<BOOT>>---
> GDB: no debug ports present
> KDB: debugger backends: ddb

OK, I (and the subject) was wrong. The loader boots, and show
following log at last:

Loading kernel...
/boot/kernel/kernel text=3D0x2a8 text=3D0x8bcbf0 text=3D0x1f97ac
data=3D0x1a6ac0 data=3D0x0+0x381000 syms=3D[0x8+0x11f6a0+0x8+0x1439ea]
Loading configured modules...
can't find '/boot/entropy'
can't find '/etc/hostid'
No valid device tree blob found!
WARNING! Trying to fire up the kernel, but no device tree blob found!
EFI framebuffer information
addr, size=C2=A0 =C2=A0 =C2=A0 =C2=A0 0x80400000, 0x7e9000
dimensions=C2=A0 =C2=A0 =C2=A01920 x 1080
stride=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01920
masks=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00ff0000, 0x0000ff00, 0x00= 0000ff, 0xff000000

and it stops here. No "<<BOOT>>" line is displayed. So, it seems that the kernel is loaded but could not be started.

There are several causes of this.

Most likely is that the console is setup to go somewhere else. Though= if you are on the video display and getting that framebuffer output, it wo= n't not go there w/o some setting to override (say to force serial).

Next most likely is that FreeBSD doesn't cope we= ll with having both FDT and ACPI information available. But since not DTB i= s being passed in (per that message) that's not likely at play here.

Finally, the loader passes a large number of tables,= etc to the kernel. It's quite possible that, for reasons still unknown= , that data is wrong or if standard conforming not expected by the kernel. = this leads to a crash before we've setup the console in the kernel whic= h looks a lot like a hang.

Warner

=C2=A0
>= . . .
>
> Such also happens for stable/13, releng/13.* based installations
> as well --and likely others too.
>
> ACPI booting does not use Device Tree information but the messages
> are output anyway about the lack. Only if you know that the context > is a Device Tree style of boot are the messages actually reporting
> a problem.
>
>
> =3D=3D=3D
> Mark Millard
> marklmi at yahoo.com
>

--000000000000fb226005ef2b25ef--