Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Feb 2018 15:57:24 -0600
From:      Kyle Evans <kevans@freebsd.org>
To:        Warner Losh <imp@bsdimp.com>
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:  <CACNAnaHL3zX7x%2B_PcLwnV0v6oEYGpHQz6akStsGUYhNevVB8pw@mail.gmail.com>
In-Reply-To: <CANCZdfp46DSgm6RBj%2BW8VCLs0ZQ6bmqZHzz2a%2BjYwssONGaduA@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> <CANCZdfp46DSgm6RBj%2BW8VCLs0ZQ6bmqZHzz2a%2BjYwssONGaduA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 19, 2018 at 3:37 PM, Warner Losh <imp@bsdimp.com> wrote:
>
>
> 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@clu=
b.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: t=
he
>> 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.
>

I've created D14442 [1] to improve this situation a little bit. We
should also either:

1.) Provide a way for lua to register a function to handle a loader command=
, or
2.) Provide a way for lua/forth to tell the common boot what modules to loa=
d.

These both entail a good amount of work and quite a few places to
fail, but one of them needs to happen. =3D(

[1] https://reviews.freebsd.org/D14442



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaHL3zX7x%2B_PcLwnV0v6oEYGpHQz6akStsGUYhNevVB8pw>