From owner-freebsd-current@freebsd.org Mon Mar 6 01:54:42 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 76051CF7F9D for ; Mon, 6 Mar 2017 01:54:42 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 437FE1E15 for ; Mon, 6 Mar 2017 01:54:41 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v261uRS8072972; Sun, 5 Mar 2017 17:56:33 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: Dexuan Cui Cc: "FreeBSD CURRENT" In-Reply-To: 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>, From: "Chris H" Subject: Re: Boot failure - svn up from this morning Date: Sun, 05 Mar 2017 17:56:33 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <8b05cb241a72525a2b5c576b861f7fda@ultimatedns.net> Content-Transfer-Encoding: 8bit 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: Mon, 06 Mar 2017 01:54:42 -0000 Thank you verymuch for the reply, Dexuan! On Mon, 6 Mar 2017 00:34:19 +0000 Dexuan Cui wrote > > From: Chris H [mailto:bsd-lists@bsdforge.com] > > > Hi Alex, > > > Thanks for the info! > > > Unluckily it looks the delay() in my patch didn't work here somehow, so > > > the screen scrolled up so quickly that we're unable to see the output > > > clearly... :-( > > > > > > Luckily we can use this new method: > > > When you reach the "OK " prompt in your screenshot > > > please run "memmap" command > > > and share the output with me. Please press space to show the complete > > > info and share the screenshots. > > > > > > E.g. in my side, the memmap command shows: > > I'm experiencing the same problem. > > I've taken several screen shots, but not sure I got all of them. > > I guess the first, and last will maybe the most important. I'll > > clean them up, and post a link to them. > > Thanks! I'm eager to see your screenshots. > The line whose "Physical" address contains 2MB is the most interesting to me. > And please at least post the other lines around the line. OK. Her you go. It's taken me some time to get any shots that are readable -- I don't have a very steady hand. :-( Anyway, I haven't touched them. They're just as my phone camera produced them. Because of their size, I've packed them all up. I'm afraid I don't know their exact order. Hopefully you'll know by looking at them. :-) They're located at: bsdforge.com/efi-memmap.tar.xz Thank you very much for all your time, and attention to this, Dexuan! And sorry for my frustration. --Chris > > > In the meantime, is there any way to get the system to boot again? > > Is it possible to simply boot the install DVD, and replace the > > efi image on the system, with the one on the install DVD. Or > > can the offending commit simply be reverted. > > > > --Chris > Yes, you can replace the broken system's bad /boot/loader.efi with a > good version. You can also revert the offending commit ("loader.efi: reduce > the size of the staging area if necessary"). > > Thanks, > -- Dexuan