Date: Sun, 05 Mar 2017 17:56:33 -0800 From: "Chris H" <bsd-lists@bsdforge.com> To: Dexuan Cui <decui@microsoft.com> Cc: "FreeBSD CURRENT" <freebsd-current@freebsd.org> Subject: Re: Boot failure - svn up from this morning Message-ID: <8b05cb241a72525a2b5c576b861f7fda@ultimatedns.net> In-Reply-To: <MWHPR03MB26693378DE5C5AA2CF0613C1BF2C0@MWHPR03MB2669.namprd03.prod.outlook.com> References: <alpine.BSF.2.20.1703022145590.27580@mail.neu.net> <ad4fcc3e2df6b2fc422004621c2de329@ultimatedns.net> <4D3C46D7-3EBF-47AE-BFFE-37ECEA4721FD@gmail.com> <a49d5cc64aeb8fd414d3e04073d05474@ultimatedns.net> <E46FA7A7-9B98-4104-A41B-1BBFB121ECD0@gmail.com> <MWHPR03MB266958E7CEA4F1B0780932A4BF2B0@MWHPR03MB2669.namprd03.prod.outlook.com> <MWHPR03MB2669C116DA3430F1AF479E42BF2B0@MWHPR03MB2669.namprd03.prod.outlook.com> <5A39D9CC-339D-47C3-918A-F91E9CCC4E3E@fh-muenster.de> <MWHPR03MB26691C9FF3665C57F8584E2FBF2B0@MWHPR03MB2669.namprd03.prod.outlook.com> <5A56F5AA-F31E-4D7B-8CF4-918EB6F8285A@gmail.com>, <MWHPR03MB2669FB3EDFDDB79AEAF0BE15BF2D0@MWHPR03MB2669.namprd03.prod.outlook.com> <9370498b79338dcfbbbc75c657e2b8b1@ultimatedns.net>, <MWHPR03MB26693378DE5C5AA2CF0613C1BF2C0@MWHPR03MB2669.namprd03.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you verymuch for the reply, Dexuan!
On Mon, 6 Mar 2017 00:34:19 +0000 Dexuan Cui <decui@microsoft.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8b05cb241a72525a2b5c576b861f7fda>