On 2/19/18 5:48 PM, Kyle Evans wrote: > > > On Feb 19, 2018 5:44 PM, "Peter Lei" <peter.lei_at_ieee.org > <mailto:peter.lei_at_ieee.org>> wrote: > > > > On 2/19/18 2:21 PM, Kyle Evans wrote: > > Hello! > > > > On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor > <listjm_at_club.fr <mailto:listjm_at_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 > <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? > > > This doesn't appear to "just work out-of-the-box" yet when EFI booting > amd64, as I still get the 'no local APIC' panic (I just tried _at_r329609). > > Under EFI and lua loader, the following is set when breaking to prompt: > hint.acpi.0.disabled=1 > Under forth loader, this is not present/set. > > In neither case is hint.acpi.0.rsdp present/set as that appears to get > set during the exec of the loaded kernel... > > I've worked around the issue by adding hint.acpi.0.disabled="0" to > loader.conf (or patching the amd64 efi loader code to explicitly clear > that hint). > > > [Apologies for broken quoting, currently mobile] > > What happens if you patch this line out? > https://svnweb.freebsd.org/base/head/stand/lua/core.lua?view=markup#l233 Ah, right - yep, commenting out that line works. > I'll have to go back and figure out what I was thinking here again. It > made sense when I wrote it, maybe explicitly disabling ACPI if it's not > immediately detected was the wrong move. =)
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:15 UTC