From nobody Tue Nov 21 03:49:07 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SZ9Nb4kctz51gkf for ; Tue, 21 Nov 2023 03:49:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SZ9Nb2sbxz3Tss for ; Tue, 21 Nov 2023 03:49:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-548a2c20f50so2822883a12.1 for ; Mon, 20 Nov 2023 19:49:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1700538558; x=1701143358; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pYTs3e9R+MZL9HwMjxHXzNGCRRo1we8umCCfjex3OtU=; b=hIh2m0bRl749Uea+COtiHchGHChbLbcQeQpnaWDUcmfl9ud0k/wO1hPC7hiUx2p3AP bdzgLk6gUgHzl2XajIfCCH+uck7ycjAfniztXYCqk0pUeqI4wQjReua7jzNQWUSH1SHI WBWy563Acie0jliouuNPQ4F86OVIOb0g5w8oebONvpTy/kdjBwe0tnBJ8aH8g/16uUBA jSEDQiw8zL+l57goJiAh/evQKF/1iz7jDp65dWv2EzZuCsRU4f1IjYSOIs6kck7Tnkn3 bDXLEIhmZd7dOHjCI5DLVIJi5yNtC+kKV9VWeLa9vJDvQEaRX6RIQCe71o1OpuVs1I4R we/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700538558; x=1701143358; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pYTs3e9R+MZL9HwMjxHXzNGCRRo1we8umCCfjex3OtU=; b=VmyPW4FMjMTu9s5SJmT4SAd2DiRZs91LS+17C6KCqvQnNpu4t6MuiQlnJnpMpnKc6+ uNHePqFsRZizcYxzE/doPhL3h6z26gtX93E9UzQSv8S621YKJ2+hbeeOVNf2SuPexj5u XPb2aKS3emmo8un1pX3Slyi537AhcuCtQMjm1IHhnJfcQ5Vsx4S3tuUn1AGF8TnJL0S2 ifUsckfJlOIHcHMPDompio4SKfOzdz7t8bSqPXEkBqimF+6Xc+OXCIsqQFihxFRV4Vk5 AipGR5VGLIRBNsCLbK2MB6R8UPCBjpO9U82mY2srJYhC8U++NOqkMHdKW3LfQJUJF9XO JWiA== X-Gm-Message-State: AOJu0Yy12+Y4W1M/QOtmgQVHhPQdjQveULjX4VH/ph1+ldA9cAc6+yBn mrefhUkYIEofIvPD4FKO7HIlQFp0da1dAru4ek3AHPcuL8kv+d3r X-Google-Smtp-Source: AGHT+IHt1w8/5Rzn7NbeEcGW3Jx4vwtPf8mFFr013fZOnRPRFBVWvU/7AeHJbZk0aRBMbGo++89NynRYjS7ZZUJlB7I= X-Received: by 2002:a50:ed08:0:b0:548:694c:fc52 with SMTP id j8-20020a50ed08000000b00548694cfc52mr784846eds.26.1700538557957; Mon, 20 Nov 2023 19:49:17 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <303be2a6-5b9b-4079-919e-03abbe33c98d@delphij.net> In-Reply-To: <303be2a6-5b9b-4079-919e-03abbe33c98d@delphij.net> From: Warner Losh Date: Mon, 20 Nov 2023 20:49:07 -0700 Message-ID: Subject: Re: HEADSUP: panic: running without device atpic requires a local APIC on UEFI systems after 0b01d45783c3 To: d@delphij.net Cc: freebsd-current@freebsd.org, rcm@freebsd.org Content-Type: multipart/alternative; boundary="000000000000ac98f2060aa17c93" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4SZ9Nb2sbxz3Tss --000000000000ac98f2060aa17c93 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Nov 20, 2023 at 8:48=E2=80=AFPM Xin Li wrote: > On 2023-11-20 19:33, Warner Losh wrote: > > > > > > On Mon, Nov 20, 2023 at 6:21=E2=80=AFPM Xin Li > > wrote: > > > > Hi, > > > > It seems that the recent improvements of ACPI detection (e0f3dc8272= 7f > > 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=3Df213da893ca8c7c76e1656b36d3a10f= 93f9a1760 > < > https://cgit.freebsd.org/src/commit/?id=3Df213da893ca8c7c76e1656b36d3a10f= 93f9a1760> > 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=3D0abe05aeac29d99786401b9078e97dc= ead35f7f3 > ) 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, > > --000000000000ac98f2060aa17c93 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Nov 20, 2023 at 8:48=E2=80=AF= PM Xin Li <delphij@delphij.net> wrote:
On = 2023-11-20 19:33, Warner Losh wrote:
>
>
> On Mon, Nov 20, 2023 at 6:21=E2=80=AFPM Xin Li <delphij@delphij.net
> <mailto:de= lphij@delphij.net>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0Hi,
>
>=C2=A0 =C2=A0 =C2=A0It seems that the recent improvements of ACPI detec= tion (e0f3dc82727f
>=C2=A0 =C2=A0 =C2=A0and 0b01d45783c3) would leave the system in an unbo= otable state if the
>=C2=A0 =C2=A0 =C2=A0UEFI files are not being updated at the same time o= f "make
>=C2=A0 =C2=A0 =C2=A0installworld".=C2=A0 At early boot the kernel = would panic with:
>
>=C2=A0 =C2=A0 =C2=A0panic: running without device atpic requires a loca= l APIC on UEFI
>=C2=A0 =C2=A0 =C2=A0systems
>
>=C2=A0 =C2=A0 =C2=A0To recover a system in this state, at loader prompt= , use:
>
>=C2=A0 =C2=A0 =C2=A0unset hint.acpi.0.disabled
>=C2=A0 =C2=A0 =C2=A0boot
>
>=C2=A0 =C2=A0 =C2=A0(I think core.lua should be modified to be compatib= le with an older
>=C2=A0 =C2=A0 =C2=A0UEFI
>=C2=A0 =C2=A0 =C2=A0payload, possibly issuing a warning that gets logge= d; and this
>=C2=A0 =C2=A0 =C2=A0should be
>=C2=A0 =C2=A0 =C2=A0mentioned in UPDATING)
>
>
> I just pushed
> https://cgit.= freebsd.org/src/commit/?id=3Df213da893ca8c7c76e1656b36d3a10f93f9a1760 &= lt;https://cgit.fr= eebsd.org/src/commit/?id=3Df213da893ca8c7c76e1656b36d3a10f93f9a1760>= 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.freeb= sd.org/src/commit/?id=3D0abe05aeac29d99786401b9078e97dcead35f7f3
) should be sufficient for x86 systems to boot.=C2=A0 Thanks!

Yes. Clicked on the wrong commit.=C2=A0 Kyle and I w= ill come up with something to allow easier transitions in the future.
=

Warner
=C2=A0
Cheers,

--000000000000ac98f2060aa17c93--