On 8/22/2016 23:01, Glen Barber wrote:> On Mon, Aug 22, 2016 at 10:53:06PM -0500, Karl Denninger wrote:
>> On 8/22/2016 22:43, Glen Barber wrote:
>>> On Thu, Aug 18, 2016 at 11:30:24PM +0000, Glen Barber wrote:
>>>> Two issues have been brought to our attention, and as a result,
11.0-RC2
>>>> builds will be delayed a day or two while these are
investigated.
>>>>
>>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211872
>>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211926
>>>>
>>>> An update will be sent if the delay is longer than anticipated.
>>>>
>>> Just an update, the 11.0-RC2 will be delayed at least two days.
One of
>>> the issues mentioned in the above PR URLs does not affect
releng/11.0,
>>> and is a non-issue, but we are awaiting one more change to the
stable/11
>>> and releng/11.0 branches that we hope will be the final major
changes to
>>> 11.0.
>>>
>>> If this is the case, we may be able to eliminate 11.0-RC3 entirely,
and
>>> still release on time (or, on time as the current schedule
suggests).
>>>
>>> However, as you know, FreeBSD releases prioritize quality over
schedule,
>>> so we may still need to adjust the schedule appropriately.
>>>
>>> So, help with testing 11.0-RC1 (or the latest releng/11.0 from svn)
is
>>> greatly appreciated.
>>>
>>> Glen
>>> On behalf of: re@
>>>
>> Has any decision been made on this?
>>
>> It is not local to me (others have reported problems with combination
>> devices) and rolling back the change in question eliminates the
>> problem. It remains un-triaged as of this point.
>>
>> Note that this impacts a system that is booting and needs manual
>> intervention, which is not a good place to a have a problem....
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211884
>>
> Well, it's an EN candidate if we cannot get it fixed before the
release.
> But, I've put it on our radar, which it was not on mine previously...
>
> Glen
Thank you.
As far as I can tell reverting that one commit (which results in just
one file being rolled back with a handful of lines) fixes it. The other
PR (which is linked in this one) reporter also reported that reverting
that same commit fixes the problem for him as well.
--
Karl Denninger
karl at denninger.net <mailto:karl at denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2996 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20160822/8bff43eb/attachment.bin>