From owner-freebsd-bugs@freebsd.org  Mon Jun  6 21:52:49 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 77094B6362F
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon,  6 Jun 2016 21:52:49 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 67A641AD7
 for <freebsd-bugs@FreeBSD.org>; Mon,  6 Jun 2016 21:52:49 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u56LqnHk004143
 for <freebsd-bugs@FreeBSD.org>; Mon, 6 Jun 2016 21:52:49 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 209944] kernel panic when trying to EFI boot from memory disk
Date: Mon, 06 Jun 2016 21:52:49 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: uefi
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: tehnerd@tehnerd.com
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: Not A Bug
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: resolution bug_status
Message-ID: <bug-209944-8-pLRpuxdxHP@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209944-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-209944-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2016 21:52:49 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209944

Nikita <tehnerd@tehnerd.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |Not A Bug
             Status|New                         |Closed

--- Comment #1 from Nikita <tehnerd@tehnerd.com> ---
The reason why mem allocation was failing is because default value of
EFI_STAGING_SIZE is 48M, and if mfsroot is bigger than that - booting fails.
building a custom loader.efi w/ value for EFI_STAGING_SIZE bigger than
mfsroot's size fixed this panic.

--=20
You are receiving this mail because:
You are the assignee for the bug.=