From owner-freebsd-current@freebsd.org Mon Dec 11 23:06:10 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 CCF06EA1E82 for ; Mon, 11 Dec 2017 23:06:10 +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 8DACB7E2E3 for ; Mon, 11 Dec 2017 23:06:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x230.google.com with SMTP id u62so20008139ita.2 for ; Mon, 11 Dec 2017 15:06:10 -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=YtrEjVLerwfbX8+DyTjhdUSf629Eevus+MZqa0kPdD4=; b=YjnME80Gd9rfM8mMLjCNUHe7tadCLC3U3gb8gixzx9jkmN5eKxnbhi+B3GvVPzYAWN n/19Izb85VPoSyaLbJZbCgxOfuOgavoakCzY7weEwa/JMPxEpQVVTDZ3xKjIinvPqs2m E7qxJQjuuPKB+ZNE6PmmPrNV9rMST392+cbkVyveISL0uVl1grZJPfqv9sLNzKY++wLW 0lNK+UPmUzHVHDUR+y1LQ89uyx0yOXtK2Yj+KDCn6tiN0fs1vqurY8fT5lxF2PzNe9nT 8EasM+zWhvz8UJtmYwZLpo5NTopQmxtEUNxOrZQ1w3pHt3pePHY0lPwTKQ93sqW6QS8h 9YDg== 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=YtrEjVLerwfbX8+DyTjhdUSf629Eevus+MZqa0kPdD4=; b=nISrVzL+UxzF1L/xlEClRq08oGFqrNGBPbkIM+ZF7INm2CP8Oyko2v2slB5LNC0PIx v5BkGU5FlJAqYnCNjRfdbqKwT0adf4sroTL4BkKunPhnkPdSj0uDYECkTs6U9Wb//VoT JRrX+cyjfGV8HdrGx+UfcJpBkIeqROdviMzPQuyxo/VrARvT1OKIAIOPoHwjuFU6e07Q ZoQfOoH0sUY86AHyBBZCpeTmFJ2EXp6JhK8RP/TEWjFvm0T56o8xkoIj7pw+39ZKneIT 7M6vzIONjNUukEDL2H2FGjnKHl3X0VHyTnAX0pWeeCy5IR9723Hss/CEeQojVGRLzOre PC9w== X-Gm-Message-State: AKGB3mJNokat6FEQGJgi/SFTCxvhcUGxtPIxLVzcfnAR3DjMpPl3TwPA /5U3SzEWsI24/OV7pbIOo/uc2QFKfb+odXaddqT5cA== X-Google-Smtp-Source: ACJfBoup2OmRVHIQEWO6CLGam9+MAVsSRneMiSRFpiSKkqaCIY/XZu9RUJDmHiJEM7eWPO/iIuDqAHahz5tO4MCueK0= X-Received: by 10.36.131.200 with SMTP id d191mr3386255ite.97.1513033569823; Mon, 11 Dec 2017 15:06:09 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Mon, 11 Dec 2017 15:06:09 -0800 (PST) X-Originating-IP: [75.104.71.74] In-Reply-To: References: From: Warner Losh Date: Mon, 11 Dec 2017 16:06:09 -0700 X-Google-Sender-Auth: oJJh5FyjL4CknjTciQ5dw0aW2sQ 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:06:10 -0000 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. >