From owner-freebsd-current@freebsd.org Mon Feb 19 20:21:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25526F2134F for ; Mon, 19 Feb 2018 20:21:35 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com [209.85.215.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9033C697CA; Mon, 19 Feb 2018 20:21:34 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f43.google.com with SMTP id v9so1132659lfa.11; Mon, 19 Feb 2018 12:21:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=CvRtpjeT5C3M0GqdGVvfPuA0n/lLsGZv7HGps93ru3g=; b=hIWh8Y1T12eKJyglHE2+m8TPLfPCH+C0Sl+jbNsSXwpB6pHOfBeLJcMC1F+HwXQERo BepbbZ7PDXZlYsCeJGEDMKoNsO/g69CSik+91C++HHkl0XlwXcMsauGaRT64gIfDXMYn MZyVIzlAb8s1WqNj5JI1AiiI3tRv729+3nOqgQ0R068wUowezYj9pzeZALxf6vxs9vWE xqoQehzO8L5a+jHNBxVK1U1TrIbFIAcY3Cn4eJTJ8ZSZOuBDgk2E/XLMNPMCOPXb+J8q ZOWprFfTEGEhQggAXUq8VFI/sV0YSs/rz9Ari1Rnjt2Xna3lboSAPsE5JULIbNW2kpwN lM3Q== X-Gm-Message-State: APf1xPAPm57pnxGAjRtt5M7ZeBL1l/Bh1LoGIlRq20ZKBSTZPlgPlRXT gecMRfu7WnRVtzYf+WnNYCWaKf34 X-Google-Smtp-Source: AH8x227DeT7RhtuRSpdRj1OR9GD2UdzG1xX5Vew2xgdmAAWbOaBdsysbjU0vF4AoWVswDJAL3t6QOw== X-Received: by 10.46.21.75 with SMTP id 11mr7538424ljv.58.1519071687004; Mon, 19 Feb 2018 12:21:27 -0800 (PST) Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com. [209.85.215.47]) by smtp.gmail.com with ESMTPSA id g17sm4461744ljf.22.2018.02.19.12.21.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Feb 2018 12:21:26 -0800 (PST) Received: by mail-lf0-f47.google.com with SMTP id t204so1136143lff.9; Mon, 19 Feb 2018 12:21:26 -0800 (PST) X-Received: by 10.46.4.74 with SMTP id 71mr633652lje.51.1519071686497; Mon, 19 Feb 2018 12:21:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.106.8 with HTTP; Mon, 19 Feb 2018 12:21:05 -0800 (PST) In-Reply-To: <1b9e58fe-2616-b04b-13c2-fee78a33ad6e@club.fr> References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> <1b9e58fe-2616-b04b-13c2-fee78a33ad6e@club.fr> From: Kyle Evans Date: Mon, 19 Feb 2018 14:21:05 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: ACPI panic on boot with new Lua loader and other minor issues To: =?UTF-8?Q?Juan_Ram=C3=B3n_Molina_Menor?= Cc: freebsd-current@freebsd.org, dteske@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Feb 2018 20:21:35 -0000 Hello! On Mon, Feb 19, 2018 at 8:21 AM, Juan Ram=C3=B3n Molina Menor 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 previo= us > message: > 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? > Also, I can not stop boot2 to try to use the copy of the Forth loader: th= e > keyboard only becomes responsive at the loader stage. Hmm... > There is an error during this stage: > > Loading /boot/defaults/loader.conf > Failed to open config: =E2=80=99/boot/loader.conf.local=E2=80=99 David's diagnosis of this is right- this is more of an informational message that you don't need to worry about. > Moreover, the "boot [kernel]" loader command does not work: > > OK ls /boot/kernel.old/kernel > /boot/kernel.old/kernel > OK boot kernel.old > Command failed > OK boot /boot/kernel.old/kernel > Command failed > OK boot kernel > Command failed > > On the other hand, just "boot" works. It seems that the Forth loader might be doing something sneaky and replacing the standard common "boot" with a Forth boot that handles this a lot better. CC'ing dteske@ so they can confirm. > Finally, the double lines drawing a frame around the loader menu do not w= ork > with the new loader and are replaced by ? characters in a box. Interesting, I'll look into that... anything interesting/unique about your setup? r329387 should have addressed one potential cause of this, but I see you're past that.