From owner-freebsd-current@freebsd.org Mon Dec 11 22:56:52 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 D11B4EA1BB4 for ; Mon, 11 Dec 2017 22:56:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 91B057DDF2 for ; Mon, 11 Dec 2017 22:56:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22e.google.com with SMTP id d137so19782489itc.2 for ; Mon, 11 Dec 2017 14:56:52 -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=Vgb6L/RmzcHJNMSC0h+1BAq2Uun0MaSys/0OP3k93wo=; b=mepfKcnGgMtVOYpQSDhnKjNwxKnrWBVQYhkWOZm37sgen32MJiydR+2oP46jxpungC Wx9eBtF2O40ioai+lpfdfgZKPeVNdXjUcJQM/86o9Y2/HNbmKRm6ifs+qBuBkdRH3SLr L621Mmkmqs/sGe5RlYCz7jEQM0r7PRRfsIg0mpfIYGymN2o7TfDI+OkhoTeJYEZ0h7ZO QuE4pkr+HV62sr0Epttq5WRIbhXymEwSIBd5D+Q41Ine9MGlgK82CCy/QDoWlLCDpKRB yuWNEvphy3QHL44m/+A7/XPgug6NfuXyUdCvyYdL0PJ+q5Q8usCjcqCdEgjB3WvOWGPU ckAQ== 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=Vgb6L/RmzcHJNMSC0h+1BAq2Uun0MaSys/0OP3k93wo=; b=QLTh2uBG84EymEQJcQlpyed+TsPuUxcF1X+6ZHGJwInsW9swQVY8R4mkwwYJVpyAnX 4PmWJT/OwvJW09J9nzsLXAW4e+1EL1WwfADHUrh38glp50qGNsw8sDKLwZV0lnyEEuC+ L43lTIo8XQLt2t+2+5tTXxHg9Q3DxoqrJV1ywdVL85lOCgdiRWZURj0jm548z5R9H9O7 wMtnm0EYWINwULgMEsCL+zY4sEDMGyRyAZah2pWvCEmfVInN7S17N7lgEiyPM/gs4Lj0 /+JPF1078zWR4mIa79TNtoSqs93EY031wwWISAkuvL8bmMYNoFonQm8zidCpvxZpYaz/ O1uw== X-Gm-Message-State: AKGB3mLBnpShRAutt45bqe6YiEyUxlN4XEdUUdOoDav5cQ3GfgIt2Y4h wmZM92Kvq7MnOJnEa2XZvZkxhTEz/vJyg4i0G55J77xk X-Google-Smtp-Source: ACJfBotOUKm0ZJXg1YOODx+5/K05pV1mtIxY08nLFoTkK6pKHecUUPbZKmUOQ9IGOKV9RIVQDqYTcJyfVW7+HvBdn+A= X-Received: by 10.36.147.193 with SMTP id y184mr3055964itd.64.1513033011793; Mon, 11 Dec 2017 14:56:51 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Mon, 11 Dec 2017 14:56:51 -0800 (PST) X-Originating-IP: [75.104.71.74] In-Reply-To: References: From: Warner Losh Date: Mon, 11 Dec 2017 15:56:51 -0700 X-Google-Sender-Auth: jEtdecLe_2wjjkn9KKcLpyxX0mY 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 22:56:52 -0000 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. > Those re related, so it makes sense they are both broken. Back up one rev (r326771) and see if that works. IT was supposed to fix some regressions from the lua import, but appears to have introduced a new regression. Warner