From owner-freebsd-current@freebsd.org Mon Dec 11 23:16:48 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 079E1EA22FA for ; Mon, 11 Dec 2017 23:16:48 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 BCBEB7EAD9 for ; Mon, 11 Dec 2017 23:16:47 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x230.google.com with SMTP id u62so20061540ita.2 for ; Mon, 11 Dec 2017 15:16:47 -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=pxQksAHfjINePI9GPfh1mFHW9aDF1OEDS7vPo7k8zSI=; b=OKv3MxMctwVUwuGCU+gIglwZkN1me7XzOBqX+FbAuL3YpyEtc4vp7pwYiJJIkA4mjp L3Ncz09wsOalGcsCuIDxU8Z0gm74uIWCiCQRRq96BFy3ipOgOudk/GZbpQt/HC44IYi8 rYMtF7hvjarAO/RPruZY9TOCfACmyv3/4uMSmi/apW7+lhB43TWfDZPZzcWAg0dfwNMG tS7Kxpr4Etsl2VcyUuoHeC8JonG69KQCkhum4fEDBTQNmdVhkiUxkicL/ydEq/7QPHqG /k+iYrriKJbarxFcaYpkxLqzSm3p3/R/Eow2lLjR0CuTPD1suuYwT1SeFjGU113SaQZ9 kCxQ== 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=pxQksAHfjINePI9GPfh1mFHW9aDF1OEDS7vPo7k8zSI=; b=YFcPI9Vt7SBVVC8F1GqF11+VwgAQbln6y26/YhfiSeejlP9GmS744U1cyfReSdDluJ DWfvcl8oMAi+UjrNfJx7KhuSRu23Daxb9Pv5WrjrO0shxFckWZ3lhuJJ2M3akl0Fpe3C lYX8KaO+eFx7MzGA9HCj3T4eUco7hB1QBBY90MuE+O0ey+VKTYYOMl/QwzL9/Qn3htfM vPC0Pw13DFNx1EHx4gmislYrLHzuMtXRtrADc0JJRHNvgVmz7LPr1LHt7GGdcJKmeTv5 Cy3zeJRwOWZ9S5Uqog39H2mHM6PhOlr91/fHzuubLLAB7qKm2xfCWPvy3w6IBepHdRI4 CVjQ== X-Gm-Message-State: AKGB3mJDOlDKAF6O1y4UawkjqEB5VfVTYEM4An9AmvoEY2dVYeb1L4DG kiQKwyWHGiM5qb1KOE7eHxGSoG16pa1zbKegqqC+WA== X-Google-Smtp-Source: ACJfBouDWWH5LoOrn1sv+GlNna9iiWWV74jT3Gzwh7r+WDipblfZitQxmib/gqiKJsy1HqUOT+GHzqQrVwQkw8lfQRI= X-Received: by 10.36.164.13 with SMTP id z13mr3494615ite.115.1513034207035; Mon, 11 Dec 2017 15:16:47 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Mon, 11 Dec 2017 15:16:46 -0800 (PST) X-Originating-IP: [75.104.71.74] In-Reply-To: References: From: Warner Losh Date: Mon, 11 Dec 2017 16:16:46 -0700 X-Google-Sender-Auth: MTMH5QCLOuG_nW9tzw8Ynq-PHzU Message-ID: Subject: Re: don't know how to load module '/boot/loader' To: Alan Somers Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" 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, 11 Dec 2017 23:16:48 -0000 Ooops I lied. r326784 should fix it. Now I have flight attendants yelling at me to put this computer away.... Warner On Mon, Dec 11, 2017 at 4:06 PM, Warner Losh wrote: > I'm seeing the same bug in my qemu VM setup. I'm about to land, so won't > likely be able to fix this until I get to the hotel, but I'm pretty sure > that I know what caused it. I didn't notice it before the commit (I gotta > get a better regression suite in place for this stuff, rather than the > ad-hoc testing I've been able to do). > > Warner > > On Mon, Dec 11, 2017 at 3:37 PM, Alan Somers wrote: > >> On Mon, Dec 11, 2017 at 3:30 PM, Warner Losh wrote: >> >>> >>> >>> On Mon, Dec 11, 2017 at 3:26 PM, Alan Somers >>> wrote: >>> >>>> On Mon, Dec 11, 2017 at 3:19 PM, Warner Losh wrote: >>>> >>>>> >>>>> >>>>> On Mon, Dec 11, 2017 at 3:03 PM, Alan Somers >>>>> wrote: >>>>> >>>>>> I just upgraded my head machine to r326772. Now, boot2 can't find the >>>>>> loader. Instead, it tries to boot the kernel directly, which fails >>>>>> because >>>>>> the ZFS module isn't loaded. If I break into boot2 and type "boot >>>>>> /boot/loader" I get the error "don't know how to load module >>>>>> '/boot/loader'". I last updated on 30-Nov, so this bug must've been >>>>>> introduced since then. Any ideas? >>>>>> >>>>>> BTW, I can successfully boot with the following commands: >>>>>> unload >>>>>> load /boot/kernel/kernel >>>>>> load zfs >>>>>> boot >>>>>> >>>>>> http://bayimg.com/iAKmFaAgl >>>>> >>>>> >>>>> I'd bisect :) >>>>> >>>>> However, try to update to just before this commit: >>>>> >>>>> Author: imp >>>>> Date: Fri Dec 8 19:57:16 2017 +0000 >>>>> >>>>> Create interp class. >>>>> >>>>> Create an interp class. Use it to separate out the different types >>>>> of >>>>> interpreters: forth and simple with function pointers rather than >>>>> via #ifdefs. >>>>> >>>>> Obtained from: lua boot loader project >>>>> (via https://bsdimp@github.com/bsdimp/freebsd.git >>>>> lua-bootloader) >>>>> Sponsored by: Netflix >>>>> >>>>> >>>>> git-svn-id: svn+ssh://svn.freebsd.org/base/head@326712 >>>>> ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f >>>>> >>>>> would be a good place to start. >>>>> >>>>> It's a shame we can't create zpool images with an unpriv'd user >>>>> command. Would help out the ZFS testing of the boot loader refinement. >>>>> >>>>> Warner >>>>> >>>> >>>> If I bisect this, what parts do I need to reinstall each time? A full >>>> buildworld would be too slow. Is it sufficient to reinstall stand? >>>> >>> >>> Just rebuild stand, reinstall it and reboot. >>> >>> Also, why are you trying to load /boot/loader from /boot/zfsloader? That >>> has me confused. The screen shot looks like it found the kernel OK and was >>> going to boot it, but then you interrupted it, unloaded it and tried to >>> load /boot/loader. Shouldn't that be /boot/kernel or /boot/kernel.old or >>> something like that? >>> >>> OK is /boot/loader's prompt (boot2 has no such prompt).... maybe the >>> real bug here is that the menu has stopped working leading to your >>> confusion... >>> >> >>> Warner >>> >> >> It certainly could be a bug in the menu. I'm definitely confused, >> because this is a domain I've seldom dealt with, since it usually just >> works. If I'm actually in /boot/loader, then there are two problems: >> 1) The menu isn't working >> 2) The loader isn't reading /boot/loader.conf. >> > >