From owner-freebsd-current@freebsd.org Sun Mar 12 11:30:04 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 D2E7FCF958D for ; Sun, 12 Mar 2017 11:30:04 +0000 (UTC) (envelope-from subbsd@gmail.com) Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (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 9698D1AA2; Sun, 12 Mar 2017 11:30:04 +0000 (UTC) (envelope-from subbsd@gmail.com) Received: by mail-io0-x244.google.com with SMTP id 68so10915141ioh.3; Sun, 12 Mar 2017 04:30:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jtQSY5WV62KtKZeF42nVXbJBr6VopHSspppoPUsKPqE=; b=kVRWuNMun/Z5ZvYF7iev5rRGpsYvT//leByhVSlmdLlrgW3CY0vAwUhea5M6IVB+FE At4426m+77KWJRjXwsxxGHEojsFYan8Li1K4x4N3wuS08KeFNeU/76Chq0/a93rfKR4I ZAAnLxRtn953LzWZdohEKqAk8F6N8ch8sFYOdHdu33Dv2JwFYLre2TOCgn5wEZOjLLc1 WlA4zCZHT7qLrLbFyAYDm8Ax6toaw+ZUhfMz6Ce6GJGmC4NcbW8WI76Mg4qC1vZ4R6Sz TrgnIEBkKenqty23LmcJ87SWeI0ZsJcV/tNMmeNX0HG0kXq8FDC4zowTT3P2Y9vmxmN/ KUKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jtQSY5WV62KtKZeF42nVXbJBr6VopHSspppoPUsKPqE=; b=JWhxXnNXDCAx6M3Fc+1ns/FX98eGxLb+lk4PviGPJDxq8qes/KCb/a+Yl7CDI7kvNB LQCtSv3nCHc1geGNIGc1xturETvqCa5IjBaym+w0uvBoJGVMcDYcJjxfwGQ3gpQxrEKY d3yPEEPLto/gmgwNCy9ypjx4eoU5VrlDU7H5e6EFaYd5hhdSLye/HQ7RQ9PK2ruuL9EG 8URjS6nDj0e41d7kQZg8OLrlsIvJF4JfVHnQ+mWr3IAmNAci7A8RH74MZ+gD+7oT3kbw 5DVBjJYiGiH6t9hWj6OnPfAgXPtJ1M+YmOSrBkFCL/N4GzCkl6fTqjDi1T4QAJZrJ4zn xv1A== X-Gm-Message-State: AMke39k5CFm6rYHfeRp6ihfg4bYTwq4NCasGCwtzfAOZAsh/r5zZfY9q+h8GMiwqVVWPu8MwMQIYKY3ziO3w1A== X-Received: by 10.107.189.68 with SMTP id n65mr23160872iof.154.1489318203844; Sun, 12 Mar 2017 04:30:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.167.24 with HTTP; Sun, 12 Mar 2017 04:30:03 -0700 (PDT) In-Reply-To: <0A045FCC-90FC-43BA-93C5-316E52E33971@FreeBSD.org> References: <4D3C46D7-3EBF-47AE-BFFE-37ECEA4721FD@gmail.com> <5A39D9CC-339D-47C3-918A-F91E9CCC4E3E@fh-muenster.de> <5A56F5AA-F31E-4D7B-8CF4-918EB6F8285A@gmail.com> <9370498b79338dcfbbbc75c657e2b8b1@ultimatedns.net> <94871692b95acb7e3ece204732a10d7f@ultimatedns.net> <497DF4FE-2E2D-482D-A96B-AC4C300EF286@FreeBSD.org> <9bc29f27d01b0c40aa6b990b9c6aacbd@ultimatedns.net> <0A045FCC-90FC-43BA-93C5-316E52E33971@FreeBSD.org> From: Subbsd Date: Sun, 12 Mar 2017 14:30:03 +0300 Message-ID: Subject: Re: Boot failure - svn up from this morning To: Jonathan Anderson Cc: Chris H , freebsd-current Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 12 Mar 2017 11:30:04 -0000 Hi, I had the same problems, however, there is one more regression after these changes. It stably reproduces if you use EFI_STAGING_SIZE. I have custom FreeBSD distributive which has a sufficiently large mfsroot which is loaded through UEFI mode. To solve the problem, it was suggested to increase this variable and rebuild /sys/boot: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209944 Also, it has to be increased periodically for some reason: https://svnweb.freebsd.org/base/stable/11/sys/boot/efi/loader/copy.c?r1=305779&r2=305778&pathrev=305779 I've try to ask why than threatens to increase this parameter at once large (or make it dependent on RAM): https://lists.freebsd.org/pipermail/freebsd-hackers/2016-November/050142.html but there are no answer options. At the moment, on r315141 boot via UEFI is fixed without EFI_STAGING_SIZE. With EFI_STAGING_SIZE=768 i got regression after last changes in panic with follow message: failed to allocate staging area:9 failed to allocate stating area Failed to start image provided by ZFS (5) http://pasteboard.co/IvbhU9Ffu.jpg I believe that there mfsroot may be greater than 64MB soon or later. Also there are no problems with loading big mfsroot images when MBR method is used. PS: I have ZFS-on-root system. With EFI_STAGING_SIZE=768 I lived with constant CURRENT svnup/rebuilds for about a year. So I will be glad if you pay attention to this. PPS: How to reproduce: 1) EFI_STAGING_SIZE=768 in /etc/make.conf 2) make -C /sys/boot clean 3) make -C /sys/boot 4) make -C /sys/boot install 5) reboot Thanks!