From owner-freebsd-current@freebsd.org Wed Aug 15 13:00:30 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 B004A108391A for ; Wed, 15 Aug 2018 13:00:30 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4C9768B08E for ; Wed, 15 Aug 2018 13:00:30 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 116EE1083918; Wed, 15 Aug 2018 13:00:30 +0000 (UTC) Delivered-To: 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 004E71083917 for ; Wed, 15 Aug 2018 13:00:30 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A55E68B085 for ; Wed, 15 Aug 2018 13:00:29 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 43AA61462A for ; Wed, 15 Aug 2018 13:00:29 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f180.google.com with SMTP id p6-v6so884061ljc.5 for ; Wed, 15 Aug 2018 06:00:29 -0700 (PDT) X-Gm-Message-State: AOUpUlECeAEVt1GoXDp1lqkAiiJoFf/rzd4JfosxNoio2rNVDzww1Its Zgr8wgToDDTu+k3ltnB4JwMgYHpzlaEhk3NsyBw= X-Google-Smtp-Source: AA+uWPyzG4+oM2bA9RSN5H8FfehUSkGSaC0XCRYjk6vVaN5ptwTvE25WH+wkKISXUCzFMuefihRhdiiKAarYd60s+XQ= X-Received: by 2002:a2e:144f:: with SMTP id 15-v6mr19194535lju.122.1534338027915; Wed, 15 Aug 2018 06:00:27 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Wed, 15 Aug 2018 06:00:07 -0700 (PDT) In-Reply-To: References: <20180815124000.GB1190@albert.catwhisker.org> From: Kyle Evans Date: Wed, 15 Aug 2018 08:00:07 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: r337738 -> r337834: Forth loader OK; Lua loader says "BTX halted" To: David Wolfskill Cc: current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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: Wed, 15 Aug 2018 13:00:30 -0000 On Wed, Aug 15, 2018 at 7:53 AM, Kyle Evans wrote: > On Wed, Aug 15, 2018 at 7:40 AM, David Wolfskill wrote: >> I'm tracking head/amd64 daily twice on each of two machines: my "build >> machine" ("freebeast") and my laptop, each first using the traditional >> Forth loader, then (on a different slice), the Lua loader. >> >> Each is using BIOS and MBR (not UEFI; not GPT). >> >> Yesterday's update was to r337738, and was uneventful for each of >> the four environments. >> >> Today's was to r337834, and was uneventful for the build machine (both >> Forth and Lua loaders -- though there remains no means of interacting >> with the loader on the build machine if it's booted using the Lua >> loader). >> >> The laptop had no issues using the Forth loader, but the boot process >> was ... severely abbreviated ... using the Lua loader. >> >> I don't have a serial consoloe on the laptop, so I snapped a photo; it >> may be found at >> . >> >> As the name suggests, the final message was: >> >> BTX halted >> >> at which point, I found no way to get the laptop to respond to anything >> but a power cycle. > > Interesting. It seems to have died in the middle of loading a > module... any insight into what that module may have been? > > Any way to hack beastie_disable="YES" into loader.conf(5) and see if > that changes things? > To be clear- the test I'm interested in will not be productive unless beastie_disable="YES" is present in loader.conf or the environment before lualoader engages at all. Thanks, Kyle Evans