Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Nov 2023 20:49:07 -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:  <CANCZdfpGT4sw4efPdYV1UBb3z5KqFN_553xLfMPiMisJ0Y=p1g@mail.gmail.com>
In-Reply-To: <303be2a6-5b9b-4079-919e-03abbe33c98d@delphij.net>
References:  <effe8ad6-40f0-4389-9a4c-49a889d6180c@delphij.net> <CANCZdfonmCpM_rtGWCC11JAPYXSJtbEUMfhfasQqpbN0HKpArg@mail.gmail.com> <303be2a6-5b9b-4079-919e-03abbe33c98d@delphij.net>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
On Mon, Nov 20, 2023 at 8:48 PM Xin Li <delphij@delphij.net> wrote:

> 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!
>

Yes. Clicked on the wrong commit.  Kyle and I will come up with something
to allow easier transitions in the future.

Warner


> Cheers,
>
>

[-- Attachment #2 --]
<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 20, 2023 at 8:48 PM Xin Li &lt;<a href="mailto:delphij@delphij.net">delphij@delphij.net</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2023-11-20 19:33, Warner Losh wrote:<br>
&gt; <br>
&gt; <br>
&gt; On Mon, Nov 20, 2023 at 6:21 PM Xin Li &lt;<a href="mailto:delphij@delphij.net" target="_blank">delphij@delphij.net</a> <br>
&gt; &lt;mailto:<a href="mailto:delphij@delphij.net" target="_blank">delphij@delphij.net</a>&gt;&gt; wrote:<br>
&gt; <br>
&gt;     Hi,<br>
&gt; <br>
&gt;     It seems that the recent improvements of ACPI detection (e0f3dc82727f<br>
&gt;     and 0b01d45783c3) would leave the system in an unbootable state if the<br>
&gt;     UEFI files are not being updated at the same time of &quot;make<br>
&gt;     installworld&quot;.  At early boot the kernel would panic with:<br>
&gt; <br>
&gt;     panic: running without device atpic requires a local APIC on UEFI<br>
&gt;     systems<br>
&gt; <br>
&gt;     To recover a system in this state, at loader prompt, use:<br>
&gt; <br>
&gt;     unset hint.acpi.0.disabled<br>
&gt;     boot<br>
&gt; <br>
&gt;     (I think core.lua should be modified to be compatible with an older<br>
&gt;     UEFI<br>
&gt;     payload, possibly issuing a warning that gets logged; and this<br>
&gt;     should be<br>
&gt;     mentioned in UPDATING)<br>
&gt; <br>
&gt; <br>
&gt; I just pushed <br>
&gt; <a href="https://cgit.freebsd.org/src/commit/?id=f213da893ca8c7c76e1656b36d3a10f93f9a1760" rel="noreferrer" target="_blank">https://cgit.freebsd.org/src/commit/?id=f213da893ca8c7c76e1656b36d3a10f93f9a1760</a>; &lt;<a href="https://cgit.freebsd.org/src/commit/?id=f213da893ca8c7c76e1656b36d3a10f93f9a1760" rel="noreferrer" target="_blank">https://cgit.freebsd.org/src/commit/?id=f213da893ca8c7c76e1656b36d3a10f93f9a1760</a>&gt; which should fix the issue for x86, with an UPDATING entry for aarch64.<br>
&gt; <br>
&gt; This is at best a stop-gap kludge. The real solution would be for <br>
&gt; loader.efi to publish a list of interfaces it implements and then the <br>
&gt; lua code can cope with old/new better.<br>
<br>
Yeah I think it (I assume you mean <br>
<a href="https://cgit.freebsd.org/src/commit/?id=0abe05aeac29d99786401b9078e97dcead35f7f3" rel="noreferrer" target="_blank">https://cgit.freebsd.org/src/commit/?id=0abe05aeac29d99786401b9078e97dcead35f7f3</a>; <br>
) should be sufficient for x86 systems to boot.  Thanks!<br></blockquote><div><br></div><div>Yes. Clicked on the wrong commit.  Kyle and I will come up with something to allow easier transitions in the future.</div><div><br></div><div>Warner</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Cheers,<br>
<br>
</blockquote></div></div>

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpGT4sw4efPdYV1UBb3z5KqFN_553xLfMPiMisJ0Y=p1g>