Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 May 2016 18:44:28 +0300
From:      Boris Samorodov <bsam@passap.ru>
To:        Andriy Gapon <avg@FreeBSD.org>, "K. Macy" <kmacy@FreeBSD.org>, FreeBSD Current <freebsd-current@FreeBSD.org>
Cc:        Alexander Motin <mav@FreeBSD.org>
Subject:   Re: boot broken on VMWare somewhere between r300069 and r300176
Message-ID:  <ab1b4869-ed22-ea27-cd09-f1ea8b77f304@passap.ru>
In-Reply-To: <4a4c783a-ae3d-fcf2-9f2b-b38b4cac13c9@FreeBSD.org>
References:  <CAHM0Q_N8aGeHr-JdkA7FcsBcCr6up-cF1Z=e2brJLT2g01HTUA@mail.gmail.com> <be3b2d82-1592-3fca-e1a4-a5161b45ee53@passap.ru> <f9929585-2f30-4140-e3b4-0c930efa8903@FreeBSD.org> <aa7a8926-13e9-daea-abe0-214e9288e33f@passap.ru> <4a4c783a-ae3d-fcf2-9f2b-b38b4cac13c9@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
19.05.16 16:43, Andriy Gapon пишет:
> On 19/05/2016 16:40, Boris Samorodov wrote:
>> 19.05.16 14:04, Andriy Gapon пишет:
>>> On 19/05/2016 13:50, Boris Samorodov wrote:
>>>> 19.05.16 09:28, K. Macy пишет:
>>>>> I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just
>>>>> did an IFC to r300176 and boot will hang right ater printing out
>>>>> "setting hostid: ". ^T just shows sh [piperd]. ddb just shows the
>>>>> shell as hanging in piperead. Diffing between those two revisions I
>>>>> don't see any obvious offenders so I'm hoping that individuals who
>>>>> have committed in the last 24 hours will have some idea of their
>>>>> changes having such an impact.
>>>>
>>>> For me (BIOS boot at DELL notebook) is broken after jump
>>>> from r300062 to r300158. CapsLock works, but ^T shows nothing.
>>>> Here is a photo (sorry for the quality):
>>>> ftp://ftp.wart.ru/pub/misc/boot_broken.jpg
>>>>
>>>> Boot with r300062 works fine.
>>>
>>> A wild guess (not really), try to revert r300113
>>
>> Tried that, conflict on reverting this single revision and an error
>> compiling kernel. (No more details, sorry, busy at work for now)
>>
> 
> Alexander has committed a fix, so upgrading to the latest version can be a
> better strategy now.

Yep, I've updated the kernel to r300212 and it works.

Thanks all!
-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ab1b4869-ed22-ea27-cd09-f1ea8b77f304>