Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Sep 2020 08:39:08 +0300
From:      Toomas Soome <tsoome@me.com>
To:        Mason Loring Bliss <mason@blisses.org>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Freeze during early boot
Message-ID:  <749DA9A0-E129-4085-BE28-A0F201883736@me.com>
In-Reply-To: <20200910005736.GB7512@blisses.org>
References:  <20200910005736.GB7512@blisses.org>

next in thread | previous in thread | raw e-mail | index | archive | help


> On 10. Sep 2020, at 03:57, Mason Loring Bliss <mason@blisses.org> =
wrote:
>=20
> Hi, all. I'd like to see FreeBSD running on a new class of box I've =
got
> here. Not new hardware. These are Atom chips on Micro-ITX =
motherboards, and
> are interesting in that they are low-power and have dual gigabit NICs.
> They're UEFI-only.
>=20
> These boxes seem to not like the FreeBSD 12.1 .iso files as written to =
USB
> sticks, but I could boot the installer with an .img.
>=20
> That said, the resulting system as installed seems to freeze in =
precisely=20
> the same place as the .iso-files-written-to-USB froze. I took a photo =
of=20
> the freeze, and then realized that it was the same as when I was =
trying to=20
> boot from the USB stick the first time.
>=20
> I've got a photo of it in the bug I've just opened to complement this=20=

> email, along with dmesg from NetBSD and Linux:
>=20
>    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249226
>=20
> What's different between the .iso and the .img files, and how might =
that=20
> translate to the installed system, if that's not a red herring? And =
how=20
> might I get these boxes to boot FreeBSD?=20

If the iso written to stick was able to give you working loader (in a =
sense that you can navigate and exit menu, enter ls, lsdev etc on loader =
OK prompt), then the iso, as bootable media, is ok.

>=20
> The boxes don't have build-in storage so I'm installing and booting =
from=20
> USB drives, so making modifications from another system to test things=20=

> ought to be fairly straightforward.
>=20
> Addendum: To try -current in case it was a known issue, I downloaded =
the=20
> mini-memstick.img, but it freezes in the same place.
>=20

Because your system is freezing while attempting to start the kernel =
(framebuffer information is printer in loader just before relocating =
loaded bits to final location and jumping to kernel, the issue can =
possibly be either in loader preparing to trampoline or in early kernel.

If you do not mind one extra test (and as you have already done =
linux/netbsd tests), I=E2=80=99d be interested to see test results from =
illumos boot (openindiana or omnios for example), press esc to get out =
from loader menu, and enter on ok prompt:=20

boot -B prom_debug=3Dtrue,kbm_debug=3Dtrue,map_debug=3Dtrue

This is useful because those systems also boot using freebsd loader, but =
there is a small difference how the kernel start is prepared, and if it =
does get that far, maybe we can get memory map from early kernel.

But to get this issue properly diagnosed and fixed, we would need to =
build test versions for your system and just see what/where we will =
get=E2=80=A6=20

rgds,
toomas=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?749DA9A0-E129-4085-BE28-A0F201883736>