Date: Fri, 10 Mar 2017 17:49:14 -0800 From: "Chris H" <bsd-lists@bsdforge.com> To: <freebsd-current@freebsd.org> Subject: Re: input/output error @boot Message-ID: <5dbe13bd7b45f0d4bbc4135532955e47@ultimatedns.net> In-Reply-To: <MWHPR03MB26696FB5963990FE4455609CBF210@MWHPR03MB2669.namprd03.prod.outlook.com> References: <CACnPvjLv_QhhxYvcbU44x=n0pk61xyFgUGWcTYh%2B6HaGUGJMFg@mail.gmail.com> <CACnPvjKG9NEuFDBWv=6qj5GZj4=-89qT8w75kEx-QaXjHNJzXg@mail.gmail.com> <6779d31b-a285-3002-8ecc-5738ac88df27@madpilot.net> <CANCZdfr_pTNuCpDx1rm9KcEimnhGTkCv3i2tNceAZsgrs_c%2BcQ@mail.gmail.com> <CANJ8om5Gri=%2B4Ju9BjdUONwQMW5zrzQhTpz2AzVWUKSVrSgdDA@mail.gmail.com> <CACnPvjJgLK-YtOTJOEE1Uad==pwzO39hSQ1Nk%2BnHND58EbTmvA@mail.gmail.com> <441BF371-53C4-4FE8-A39C-BFA8B25DE760@freebsd.org> <CACnPvjK%2Bb6x3SAD7Gu7uFTkx=iCm2afgt4boVquTT5BC_sF4Tg@mail.gmail.com> <MWHPR03MB2669AB5FFC455EE6BBAAE765BF2F0@MWHPR03MB2669.namprd03.prod.outlook.com> <CACnPvj%2BvrkYGR3b_CoDkORksB6ENZ5HLdzD6=ebJm1329LcfJQ@mail.gmail.com> <CACnPvj%2BQDZZjHzwU7VcsNFN784R4=gYe6qzhQb0NG0AQpov=5g@mail.gmail.com> <MWHPR03MB26699DF5E658361614D71A5EBF2E0@MWHPR03MB2669.namprd03.prod.outlook.com> <CACnPvjKW8di44raA=MxEbqfNPkYaoQ5uOCkgcT3tf1i733i1KA@mail.gmail.com> <CACnPvjJnTyxQu-4-MYB3rPWGZ4TJa%2B=niLkKdtaNTiO%2Bbw=hug@mail.gmail.com> <MWHPR03MB2669510547F2244091F676BCBF210@MWHPR03MB2669.namprd03.prod.outlook.com>, <MWHPR03MB26696FB5963990FE4455609CBF210@MWHPR03MB2669.namprd03.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 9 Mar 2017 06:00:23 +0000 Dexuan Cui <decui@microsoft.com> wrote > Hi Roberto, > Thanks for sending me your memmap and this is a temporary workaround > patch for you: > https://github.com/dcui/freebsd/commit/0edd1db55fbbb56352d6024250e4ae7dd8ad31 > e3.patch > > I put the memmap info here for people who're interested: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211746#c26 > > We can notice there is a 4MB BootServicesCode range at [12MB, 16MB) . > loader.efi just writes into this range by force -- this is unsafe anyway! > > To fix this correctly & thoroughly, IMO we need a relocatable kernel, but > that would require a lot of complicated long term work: > https://reviews.freebsd.org/D9686?id=25414#inline-56969 > > For now, I suggest we should only apply the idea "reduce the size of the > staging area if necessary" to VM running on Hyper-V, we should restore the > old behavior on physical machines since that has been working for people > for a long period of time, though it's potentially unsafe. > > I think in the loader we can use CPUID to tell if we're running on Hyper-V or > not. Indeed that will provide *capability*. But I'm don't think that can tell you that it is currently *enabled* || *in use*. The CPU I experienced the (u)efi issue on has the capability, but I've turned it off, as it's more hindrance for performance, for the server' intended use. IOW I think just probing for *capability* isn't going to be enough. --Chris > > Thanks, > -- Dexuan > > > -----Original Message----- > > From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd- > > current@freebsd.org] On Behalf Of Dexuan Cui > > Sent: Thursday, March 9, 2017 10:44 > > To: Roberto Rodriguez Jr <rob.rodz.jr9@gmail.com> > > Cc: FreeBSD Current <freebsd-current@freebsd.org> > > Subject: RE: input/output error @boot > > > > Hmm, Alex did report 314891 worked. > > > > Can you please post the full boot log of the loader? > > Especially, when you see the “OK” prompt, can you please run the “memmap” > > command like this link ... > > > > You can take a photo of the screen and send it to me, if it’s too big. > > > > Thanks, > > -- Dexuan >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5dbe13bd7b45f0d4bbc4135532955e47>