Date: Thu, 11 Sep 2014 10:12:37 -0400 From: Ed Maste <emaste@freebsd.org> To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= <dumbbell@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: UEFI boot failure: BIOS smap did not include a basemem segment! Message-ID: <CAPyFy2C%2B6uNv=nOBBD%2BStffTgHxJDpKTgrc--paj85EMdwFwcA@mail.gmail.com> In-Reply-To: <54109FC4.70105@FreeBSD.org> References: <54109FC4.70105@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10 September 2014 15:00, Jean-S=C3=A9bastien P=C3=A9dron <dumbbell@freeb=
sd.org> wrote:
> Hello!
>
> I tried the following FreeBSD snapshot on my Clevo W860CU with UEFI
> enabled:
> FreeBSD-11.0-CURRENT-amd64-20140903-r270990-memstick.img
Thanks for trying it out.
> The boot fails early with the following error:
> panic: BIOS smap did not include a basemem segment!
This panic means the memory map does not include usable memory (for
the kernel) with physaddr 0.
if (physmap[i] =3D=3D 0x00000000) {
basemem =3D physmap[i + 1] / 1024;
basemem =3D=3D 0 produces the panic.
The requirement for a usable memory range with physaddr 0 doesn't hold
for UEFI, and the md startup hasn't yet been reworked to accommodate
that.
> Here's a video of a verbose boot (the quality is really low, I can try
> to redo it if this one doesn't help):
> http://www.dumbbell.fr/~dumbbell/FreeBSD-Clevo-W860CU-UEFI-no-basemem-seg=
ment.mov
Pausing the video immediately after the kernel starts confirms this:
the UEFI firmware has RuntimeServicesData at physaddr 0, so not
available for kernel use.
Do you mind submitting a PR to keep track of this issue?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2C%2B6uNv=nOBBD%2BStffTgHxJDpKTgrc--paj85EMdwFwcA>