Re: HEADSUP: panic: running without device atpic requires a local APIC on UEFI systems after 0b01d45783c3
- Reply: Warner Losh : "Re: HEADSUP: panic: running without device atpic requires a local APIC on UEFI systems after 0b01d45783c3"
- In reply to: Warner Losh : "Re: HEADSUP: panic: running without device atpic requires a local APIC on UEFI systems after 0b01d45783c3"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 21 Nov 2023 03:47:59 UTC
On 2023-11-20 19:33, Warner Losh wrote: > > > On Mon, Nov 20, 2023 at 6:21 PM Xin Li <delphij@delphij.net > <mailto:delphij@delphij.net>> wrote: > > Hi, > > It seems that the recent improvements of ACPI detection (e0f3dc82727f > and 0b01d45783c3) would leave the system in an unbootable state if the > UEFI files are not being updated at the same time of "make > installworld". At early boot the kernel would panic with: > > panic: running without device atpic requires a local APIC on UEFI > systems > > To recover a system in this state, at loader prompt, use: > > unset hint.acpi.0.disabled > boot > > (I think core.lua should be modified to be compatible with an older > UEFI > payload, possibly issuing a warning that gets logged; and this > should be > mentioned in UPDATING) > > > I just pushed > https://cgit.freebsd.org/src/commit/?id=f213da893ca8c7c76e1656b36d3a10f93f9a1760 <https://cgit.freebsd.org/src/commit/?id=f213da893ca8c7c76e1656b36d3a10f93f9a1760> which should fix the issue for x86, with an UPDATING entry for aarch64. > > This is at best a stop-gap kludge. The real solution would be for > loader.efi to publish a list of interfaces it implements and then the > lua code can cope with old/new better. Yeah I think it (I assume you mean https://cgit.freebsd.org/src/commit/?id=0abe05aeac29d99786401b9078e97dcead35f7f3 ) should be sufficient for x86 systems to boot. Thanks! Cheers,