Date: Thu, 20 Sep 2012 00:54:49 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: Ian Lepore <freebsd@damnhippie.dyndns.org> Cc: freebsd-current@freebsd.org Subject: Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection Message-ID: <1859311530.20120920005449@serebryakov.spb.ru> In-Reply-To: <1348087584.95562.55.camel@revolution.hippie.lan> References: <80840563.20120920002200@serebryakov.spb.ru> <1252171344.20120920003724@serebryakov.spb.ru> <1348087584.95562.55.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Ian. You wrote 20 =D3=C5=CE=D4=D1=C2=D2=D1 2012 =C7., 0:46:24: IL> Yes, exactly. I updated the PR to request that my patch not get IL> committed because it locks up virtualbox. I hope to find time soon to IL> learn enough about installing/configuring virtualbox to figure out what IL> the problem is (offhand,I suspect it hangs in the loop that probes for IL> the need to re-index, because vbox doesn't quite emulate the hardware IL> behavior fully). How could I help? Is it possible to debug kernel on such early stage? --=20 // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1859311530.20120920005449>