From owner-freebsd-current@freebsd.org Tue Dec 12 00:07:08 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 A458EE80A79 for ; Tue, 12 Dec 2017 00:07:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (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 552EF80607 for ; Tue, 12 Dec 2017 00:07:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x229.google.com with SMTP id d16so20144411itj.1 for ; Mon, 11 Dec 2017 16:07:08 -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=/9mn3zlGiLk8W6nlmojznpnei1mCEDNbtQoLygRo9hI=; b=0roBF8tpc+kTlQRUiIXbxF2YjLp4aYfP+gNXqUvXXwPqZ5VcGJpucZeUAbYcmeXM1d mqOTMMYDFgOOFvNEhKk0LsXHckb6/Gs0U6FgJPFedbOfSkjnAV1/vCgsu+k9db4c4Aw0 Hqp5y24/hY7rqnQUO3nX8rlcpVTLSUOohGx29eP73g8tgVcjvTjbUPTb3CAK0KG3Vqv7 tY3mrAkGhopWW6PJFRC1Kmz6iOrjHfT1Xa1OvUX3+g82r5hD/QCuc34JnAlXMtXZ1+Om GmLr2SkfePjPz9wCr+rOLj6yT6JCX8Vm0bE8b0Dkary4UXKs3Eagv/dCW17ToRWwPdby usRQ== 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=/9mn3zlGiLk8W6nlmojznpnei1mCEDNbtQoLygRo9hI=; b=rUQarztSMARqMdlnfQFOfg33mxvr0yz9Z4ExUBM/lyVjY1f7eKL4NNm8AHdMWkpGm0 hwDaUtKrG735VdEI3j5kDVYplc8hB5RsPa1wlJ6Suybvd4eajF4/727mom2K6ouQpl3X EwJD4ktGMTJ8/Ifpb+VTjGx7kpsakjuuRJFV4p86quW0tl3xAdDRA54gZXBYCmK5E82P ny/OzTwiBRSeUF4dqUB5U0ktu1x7npS2DFo0M3i7mcqGes73Vc46o5zOu6xOxpef2xS6 HWVyvv+Rofd2e8N2/E7OjAGFCMG/uxW1NWlpsyLOr/J+TDQx/Pikq2FROALVpKgDepjj kenw== X-Gm-Message-State: AKGB3mL2NO7bu1rHXTx5AP60uCCSSp81f/ubqDFMS1i6d1dsRueMmgJM pIJAoB/z1U3W7gZZML/gL3WvKp/oi/NP3d812cKDvw== X-Google-Smtp-Source: ACJfBovhgwpj+AsXCVV7+wMsGdFb0Z0EEJALOlebmPJ7WbPFXtD028mNeNbwWKiWeu1IC5imrxan+DZsfMW5oJ7J5AM= X-Received: by 10.107.81.24 with SMTP id f24mr2809650iob.63.1513037227564; Mon, 11 Dec 2017 16:07:07 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Mon, 11 Dec 2017 16:07:06 -0800 (PST) X-Originating-IP: [107.77.211.234] In-Reply-To: References: From: Warner Losh Date: Mon, 11 Dec 2017 17:07:06 -0700 X-Google-Sender-Auth: un32tS0i_HC-CEBuyyqGodkM-PQ 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: Tue, 12 Dec 2017 00:07:08 -0000 You're welcome. Sorry for the hassle. Warner On Mon, Dec 11, 2017 at 4:33 PM, Alan Somers wrote: > Yep, I can confirm that r326772 introduced the bug, and it is fixed by > r326784. Thanks for the quick turnaround. > > -Alan > > > On Mon, Dec 11, 2017 at 4:16 PM, Warner Losh wrote: > >> 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. >>>> >>> >>> >> >