Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Feb 2018 06:39:41 -0800
From:      David Wolfskill <david@catwhisker.org>
To:        Juan =?iso-8859-1?Q?Ram=F3n?= Molina Menor <listjm@club.fr>
Cc:        freebsd-current@freebsd.org
Subject:   Re: ACPI panic on boot with new Lua loader and other minor issues
Message-ID:  <20180219143941.GA1212@albert.catwhisker.org>
In-Reply-To: <1b9e58fe-2616-b04b-13c2-fee78a33ad6e@club.fr>
References:  <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> <1b9e58fe-2616-b04b-13c2-fee78a33ad6e@club.fr>

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

--jIdBwf7/i7YThJrI
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 19, 2018 at 03:21:50PM +0100, Juan Ram=C3=B3n Molina Menor wrot=
e:
> I have done a full build of r329555 to test the new Lua boot loader.
>=20
> Both the new and the old kernels panic after being loaded with:
>=20
> panic: running without device atpic requires a local APIC
>=20
> For reasons unknown, ACPI is off, as shown by David Wolfskill in a=20
> previous message:
> https://lists.freebsd.org/pipermail/freebsd-current/2018-February/068497.=
html

That has been fixed (for me, at least).  My last two build/smoke-tests
were at r329517 and r329561; I believe that r329366 was the fix for ACPI
detection/setting.

> OK show hint.acpi.0.disabled
> 1
>=20
> Setting ACPI to On resolves the issue.
>=20
> Also, I can not stop boot2 to try to use the copy of the Forth loader:=20
> the keyboard only becomes responsive at the loader stage.

> There is an error during this stage:
>=20
> Loading /boot/defaults/loader.conf
> Failed to open config: =E2=80=99/boot/loader.conf.local=E2=80=99

IIUC, that's merely an informational message, not an error.  (None of my
systems have a /boot/loader.conf.local, either.)

> Moreover, the "boot [kernel]" loader command does not work:
>=20
> OK ls /boot/kernel.old/kernel
>      /boot/kernel.old/kernel
> OK boot kernel.old
> Command failed
> OK boot /boot/kernel.old/kernel
> Command failed
> OK boot kernel
> Command failed
>=20
> On the other hand, just "boot" works.

And the Lua loader permits kernel selection, as well (as the Forth
laoder has).

> Finally, the double lines drawing a frame around the loader menu do not=
=20
> work with the new loader and are replaced by ? characters in a box.

That has also been fixed for me (as of r329517).

> Hope it helps,
> Juan
> ....

Peace,
david
--=20
David H. Wolfskill				david@catwhisker.org
The circus around that memo helps confirm that Mr. Trump is unfit for offic=
e.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

--jIdBwf7/i7YThJrI
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlqK4a1fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND
QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ
7hd5Lwf/YutOzTKgqjLHVvSYN0xhNJyP+ZjuekiiCisZ4kfgMCLfY9fx7b7W3LJN
jGEj3yhCvEFnzkIy4dW4KT1mMWt4Us9s77t7dwkhImLMUoMNOmQ8jew/Wx8hju8J
8RpXgrIGNdo0Luty6T8hmp/1Xqhw6g0K7HRdq8fyWwGRHN3LvjJbybq4a/tJEcFb
qSgOznJfoXdTNqeXWqUuXHSRm/JlDuLV+JcuTSvsw+mVJ3oKC6SHwFM1FFobNSXX
sMTPNXqjQPEqWUdz5y8vLazttkSrglRNXgCOBZRR0UUAXEDASpxGef2YaO/cpgje
du83GguA3zUpaJxHM1hOyuIfw5HNkg==
=3J6K
-----END PGP SIGNATURE-----

--jIdBwf7/i7YThJrI--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180219143941.GA1212>