From owner-freebsd-current@freebsd.org Sat Mar 11 01:49:08 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 6D13BD07732 for ; Sat, 11 Mar 2017 01:49:08 +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 411E4CC5 for ; Sat, 11 Mar 2017 01:49:07 +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 v2B1n8Du099853 for ; Fri, 10 Mar 2017 17:49:14 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: <6779d31b-a285-3002-8ecc-5738ac88df27@madpilot.net> <441BF371-53C4-4FE8-A39C-BFA8B25DE760@freebsd.org> , From: "Chris H" Subject: Re: input/output error @boot Date: Fri, 10 Mar 2017 17:49:14 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <5dbe13bd7b45f0d4bbc4135532955e47@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: Sat, 11 Mar 2017 01:49:08 -0000 On Thu, 9 Mar 2017 06:00:23 +0000 Dexuan Cui 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 > > Cc: FreeBSD Current > > 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 >