Date: Mon, 20 Nov 2023 20:33:29 -0700 From: Warner Losh <imp@bsdimp.com> To: d@delphij.net Cc: freebsd-current@freebsd.org, rcm@freebsd.org Subject: Re: HEADSUP: panic: running without device atpic requires a local APIC on UEFI systems after 0b01d45783c3 Message-ID: <CANCZdfonmCpM_rtGWCC11JAPYXSJtbEUMfhfasQqpbN0HKpArg@mail.gmail.com> In-Reply-To: <effe8ad6-40f0-4389-9a4c-49a889d6180c@delphij.net> References: <effe8ad6-40f0-4389-9a4c-49a889d6180c@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000c8fccd060aa144fd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Nov 20, 2023 at 6:21=E2=80=AFPM Xin Li <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=3Df213da893ca8c7c76e1656b36d3a10f93= f9a1760 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. Warner --000000000000c8fccd060aa144fd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Nov 20, 2023 at 6:21=E2=80=AF= PM Xin Li <<a href=3D"mailto:delphij@delphij.net">delphij@delphij.net</a= >> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px= 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,= <br> <br> It seems that the recent improvements of ACPI detection (e0f3dc82727f <br> and 0b01d45783c3) would leave the system in an unbootable state if the <br> UEFI files are not being updated at the same time of "make <br> installworld".=C2=A0 At early boot the kernel would panic with:<br> <br> panic: running without device atpic requires a local APIC on UEFI systems<b= r> <br> To recover a system in this state, at loader prompt, use:<br> <br> unset hint.acpi.0.disabled<br> boot<br> <br> (I think core.lua should be modified to be compatible with an older UEFI <b= r> payload, possibly issuing a warning that gets logged; and this should be <b= r> mentioned in UPDATING)<br></blockquote><div><br></div><div>I just pushed=C2= =A0<a href=3D"https://cgit.freebsd.org/src/commit/?id=3Df213da893ca8c7c76e1= 656b36d3a10f93f9a1760">https://cgit.freebsd.org/src/commit/?id=3Df213da893c= a8c7c76e1656b36d3a10f93f9a1760</a> which should fix the issue for x86, with= an UPDATING entry for aarch64.</div><div><br></div><div>This is at best a = stop-gap kludge. The real solution would be for loader.efi to publish a lis= t of interfaces it implements and then the lua code can cope with old/new b= etter.</div><div><br></div><div>Warner=C2=A0</div></div></div> --000000000000c8fccd060aa144fd--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfonmCpM_rtGWCC11JAPYXSJtbEUMfhfasQqpbN0HKpArg>