Date: Wed, 19 Sep 2012 14:00:59 -0700 From: Adrian Chadd <adrian@freebsd.org> To: lev@freebsd.org Cc: Ian Lepore <freebsd@damnhippie.dyndns.org>, 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: <CAJ-VmokF=JK=TS34CdHqO5BTh6WN950tdK0C%2BUOWpFoQhTHhYA@mail.gmail.com> In-Reply-To: <1859311530.20120920005449@serebryakov.spb.ru> References: <80840563.20120920002200@serebryakov.spb.ru> <1252171344.20120920003724@serebryakov.spb.ru> <1348087584.95562.55.camel@revolution.hippie.lan> <1859311530.20120920005449@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19 September 2012 13:54, Lev Serebryakov <lev@freebsd.org> wrote: > 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 t= o > IL> learn enough about installing/configuring virtualbox to figure out wh= at > IL> the problem is (offhand,I suspect it hangs in the loop that probes fo= r > 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? Add something to atrtc_start() to only loop over that loop say, 64k times before dropping out; and print an error if it hits that condition. Also, what's that RTCSA_8192 bit do? adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokF=JK=TS34CdHqO5BTh6WN950tdK0C%2BUOWpFoQhTHhYA>