Date: Thu, 19 May 2016 14:04:59 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Boris Samorodov <bsam@passap.ru>, "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: <f9929585-2f30-4140-e3b4-0c930efa8903@FreeBSD.org> In-Reply-To: <be3b2d82-1592-3fca-e1a4-a5161b45ee53@passap.ru> References: <CAHM0Q_N8aGeHr-JdkA7FcsBcCr6up-cF1Z=e2brJLT2g01HTUA@mail.gmail.com> <be3b2d82-1592-3fca-e1a4-a5161b45ee53@passap.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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 -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f9929585-2f30-4140-e3b4-0c930efa8903>