From owner-freebsd-current@freebsd.org Mon Feb 19 21:37:20 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 A2F35F0040D for ; Mon, 19 Feb 2018 21:37:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::242]) (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 3B9686C7AD for ; Mon, 19 Feb 2018 21:37:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x242.google.com with SMTP id l12so6999724ioc.10 for ; Mon, 19 Feb 2018 13:37:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=KWYUvrPJ8oW9ofIrb86XaCZAS5y+16Kb+sV/NaFj7QQ=; b=ClYAe/Mjp7gmrJajFsfrCUVJfXZExPqlTRkm8rF/g3aQ0BJ7nrQ7EOX0taN8i3NZ3X NcnLk+B3cejgOD+7DTsjlgN6EtD3zhc+/YocrLqOrPXEZ9LoakNfzPTYikLNvlC4+oUW JeqWFlVSGNHYDFKrBtYdC/tRamfb2XnJN9vDrleNvLOBCgr8EDMF2YdDcgwBtGHghPbW q/9RUUs3xzPhrBBhpqOXZEZ1xHp+0udRdmpnUvS05HTfNcYkG3xtYgjPgAnDu/+B3JX5 I4YschjhoS5Btzicj4LgkuggkuwGxSXq+QhFvSDqlAAKwfXHTcnc0arKETt4D6in9uNb 9rew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=KWYUvrPJ8oW9ofIrb86XaCZAS5y+16Kb+sV/NaFj7QQ=; b=m0bshbfAW+RtT2UPH3WUDHc5o3W042a+ee8y1NCN8DdZG1KU9zqCKweTuFGXVUvtmD EqrPvyE/+rBm+T4DiRCTQhWFjuSDcTSOFjNfszeJ8Hsl5glAwLLBWx2JLOeL3qJKYK6I zsEXq4tTB8nXYEcckwyzACJZLSoeFbp+CiirRrAtOalLu+BUVDmLKylUtrDNIcSRSQvs 6G2pHSuo5Xsi5kv5OuKzOKVqiCQGw54hN5vlNG0dSdOD3upP0OwI8GVkwqlvU28CiJDZ Zyo18UEZFTSzxZG4ADhFatbtNj6uorLc936JPb4tQH4YJcbP3wB6GaiqD0m0WNgohIpQ AlwA== X-Gm-Message-State: APf1xPDw5RYk2cqzXWD/8uedjdE62N64Wg0Bwl3gbsGQDUgVFEXG/+Ao CdQLflZTT6ZxloPFhC3rMnpE7bexHpVO/Lb/7/99lw== X-Google-Smtp-Source: AH8x227fAdJSXo+ODSS6M4CYRtLcVaId7ajbtgYTWZKwczhGq29dLSZfNL48BJPZGXqTzdC4Cw7TetfALAIzzd27Fo4= X-Received: by 10.107.2.6 with SMTP id 6mr21163639ioc.117.1519076239359; Mon, 19 Feb 2018 13:37:19 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Mon, 19 Feb 2018 13:37:18 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:9198:c568:89aa:9c67] Received: by 10.79.201.67 with HTTP; Mon, 19 Feb 2018 13:37:18 -0800 (PST) In-Reply-To: References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> <1b9e58fe-2616-b04b-13c2-fee78a33ad6e@club.fr> From: Warner Losh Date: Mon, 19 Feb 2018 14:37:18 -0700 X-Google-Sender-Auth: pRELEbh5d_SOSIpvJkceAuGdLtc Message-ID: Subject: Re: ACPI panic on boot with new Lua loader and other minor issues To: Kyle Evans Cc: =?UTF-8?Q?Juan_Ram=C3=B3n_Molina_Menor?= , FreeBSD Current , dteske@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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 21:37:20 -0000 On Feb 19, 2018 1:23 PM, "Kyle Evans" wrote: 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 previous > 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. Indeed, it does. Loader.4th defines boot. Search for ': boot' to see it. Warner > Finally, the double lines drawing a frame around the loader menu do not work > 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. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"