Date: Mon, 19 Feb 2018 14:37:18 -0700 From: Warner Losh <imp@bsdimp.com> To: Kyle Evans <kevans@freebsd.org> Cc: =?UTF-8?Q?Juan_Ram=C3=B3n_Molina_Menor?= <listjm@club.fr>, FreeBSD Current <freebsd-current@freebsd.org>, dteske@freebsd.org Subject: Re: ACPI panic on boot with new Lua loader and other minor issues Message-ID: <CANCZdfp46DSgm6RBj%2BW8VCLs0ZQ6bmqZHzz2a%2BjYwssONGaduA@mail.gmail.com> In-Reply-To: <CACNAnaFNv5LwDv3Z2dgPe%2Bb%2B3La%2B%2B-4CPNECug5XCdaTT_uo3A@mail.gmail.com> References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> <1b9e58fe-2616-b04b-13c2-fee78a33ad6e@club.fr> <CACNAnaFNv5LwDv3Z2dgPe%2Bb%2B3La%2B%2B-4CPNECug5XCdaTT_uo3A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 19, 2018 1:23 PM, "Kyle Evans" <kevans@freebsd.org> wrote: Hello! On Mon, Feb 19, 2018 at 8:21 AM, Juan Ram=C3=B3n Molina Menor <listjm@club.= fr> wrote: > I have done a full build of r329555 to test the new Lua boot loader. > > Both the new and the old kernels panic after being loaded with: > > panic: running without device atpic requires a local APIC > > For reasons unknown, ACPI is off, as shown by David Wolfskill in a previous > message: > https://lists.freebsd.org/pipermail/freebsd-current/ 2018-February/068497.html > > OK show hint.acpi.0.disabled > 1 > > Setting ACPI to On resolves the issue. As David noted, this should actually Just Work (TM) now. Can you break into a loader prompt with just the forth loader and tell me what "show hint.acpi.0.rsdp" looks like? > Also, I can not stop boot2 to try to use the copy of the Forth loader: th= e > keyboard only becomes responsive at the loader stage. Hmm... > There is an error during this stage: > > Loading /boot/defaults/loader.conf > Failed to open config: =E2=80=99/boot/loader.conf.local=E2=80=99 David's diagnosis of this is right- this is more of an informational message that you don't need to worry about. > Moreover, the "boot [kernel]" loader command does not work: > > 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 > > On the other hand, just "boot" works. It seems that the Forth loader might be doing something sneaky and replacing the standard common "boot" with a Forth boot that handles this a lot better. CC'ing dteske@ so they can confirm. Indeed, it does. Loader.4th defines boot. Search for ': boot' to see it. Warner > Finally, the double lines drawing a frame around the loader menu do not work > with the new loader and are replaced by ? characters in a box. Interesting, I'll look into that... anything interesting/unique about your setup? r329387 should have addressed one potential cause of this, but I see you're past that. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfp46DSgm6RBj%2BW8VCLs0ZQ6bmqZHzz2a%2BjYwssONGaduA>