Re: input/output error _at_boot

From: Pete Wright <pete_at_nomadlogic.org>
Date: Thu, 9 Mar 2017 08:10:57 -0800
On 3/9/17 4:42 AM, Dexuan Cui wrote:
>> From: owner-freebsd-current_at_freebsd.org [mailto:owner-freebsd-
>> current_at_freebsd.org] On Behalf Of Pete Wright
>> Sent: Thursday, March 9, 2017 14:04
>> To: freebsd-current_at_freebsd.org
>> Subject: Re: input/output error _at_boot
>> On 3/8/17 10:00 PM, Dexuan Cui wrote:
>>> 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.
>>>
>> +1
>>
>> i'd like to see the old behaviour for physical machines to be restored
>> as well since this has rendered my drm-next test rig broken :(
>>
>> -pete
>
> Eventually I committed 314956 for the issue:
> https://svnweb.freebsd.org/base?view=revision&revision=314956
> The old behaviour for physical machines are restored.
>
> PS, I understand usually I should put the patch on phabricator for review,
> before it's committed, but since the issue here is critical, I committed it
> directly to unblock people first. Sorry.
> Please comment on the patch if you think it needs rework  -- I hope not. :-)
>

Thank you Dexuan - I will do a build today and reboot when I am home 
from work tonight.  FWIW I verified that if I boot my system with in 
"classic" BIOS mode I am able to load the kernel and go multi-user, so 
this is probably the fix for me.

Cheers!
-pete

-- 
Pete Wright
pete_at_nomadlogic.org
_at_nomadlogicLA
Received on Thu Mar 09 2017 - 15:10:59 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:10 UTC