From owner-freebsd-current@freebsd.org Mon Feb 19 21:57:49 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 6358DF0210B for ; Mon, 19 Feb 2018 21:57:49 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com [209.85.215.47]) (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 C19526D9F8; Mon, 19 Feb 2018 21:57:48 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f47.google.com with SMTP id q69so1428317lfi.10; Mon, 19 Feb 2018 13:57:48 -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=a87DtU9sc2kwUaoESJKz/GdaSjSBZMglN6kxzHvG/rc=; b=HpROS3PZWlNGP70t0sql7rZi3vh6meJqAyDlrfB3lOR3oex+Oec6t2sWu2zTxnrDEr IAPA86DRg7QjEP+Rmlswn0nkeWNig59uAm7TaMO4A686rXX51muo4V7o0VS3ZGW+UkHS ujnGsXSOQI6szZEIsYngLEiZvxmO2rRW9mNQwqsrO9Qb/MH4+H1CP/6OedgDnNM2YVqQ q+zEacSB2oYO1Kh7vu9N0P76DcIek9otuXGAL3MMWIyAH+Bf3KkB7/5UYoD0f2knfQG1 zqPrFle4HgVoEQ8ASYf7baeuBkxzooEtFivicgQHCP9ChvKsYnrJarLv8yB72rwp5qOE BPEg== X-Gm-Message-State: APf1xPBmMaEqL4X9hHawRmOLAvrub3+VKwmONczdB3tm7UKvkiAci8I1 x4sac0OutwWAwEnI86PqjOOGO/k8 X-Google-Smtp-Source: AH8x225y0edt9AvNGNHpXt9W2XcQY+v/2mKp86DUX7tS5YggiDr0559GA0oHU7cPZU9cEzqWPVxzUQ== X-Received: by 10.46.89.213 with SMTP id g82mr10871921ljf.105.1519077466629; Mon, 19 Feb 2018 13:57:46 -0800 (PST) Received: from mail-lf0-f50.google.com (mail-lf0-f50.google.com. [209.85.215.50]) by smtp.gmail.com with ESMTPSA id l193sm5187275lfg.50.2018.02.19.13.57.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Feb 2018 13:57:45 -0800 (PST) Received: by mail-lf0-f50.google.com with SMTP id h78so1445741lfg.6; Mon, 19 Feb 2018 13:57:45 -0800 (PST) X-Received: by 10.46.29.69 with SMTP id d66mr5156262ljd.22.1519077465104; Mon, 19 Feb 2018 13:57:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.106.8 with HTTP; Mon, 19 Feb 2018 13:57:24 -0800 (PST) In-Reply-To: References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> <1b9e58fe-2616-b04b-13c2-fee78a33ad6e@club.fr> From: Kyle Evans Date: Mon, 19 Feb 2018 15:57:24 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: ACPI panic on boot with new Lua loader and other minor issues To: Warner Losh 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-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:57:49 -0000 On Mon, Feb 19, 2018 at 3:37 PM, Warner Losh wrote: > > > 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: t= he >> 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. > I've created D14442 [1] to improve this situation a little bit. We should also either: 1.) Provide a way for lua to register a function to handle a loader command= , or 2.) Provide a way for lua/forth to tell the common boot what modules to loa= d. These both entail a good amount of work and quite a few places to fail, but one of them needs to happen. =3D( [1] https://reviews.freebsd.org/D14442