Date: Thu, 04 Oct 2012 14:46:03 -0600 From: Ian Lepore <freebsd@damnhippie.dyndns.org> To: Marek Salwerowicz <marek_sal@wp.pl> Cc: lev@freebsd.org, freebsd-current@freebsd.org Subject: Re: [SPAM]Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection Message-ID: <1349383564.2363.111.camel@revolution.hippie.lan> In-Reply-To: <506DF061.4080403@wp.pl> References: <80840563.20120920002200@serebryakov.spb.ru> <506C8F4F.3040703@wp.pl> <13310645740.20121004225119@serebryakov.spb.ru> <506DF061.4080403@wp.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2012-10-04 at 22:24 +0200, Marek Salwerowicz wrote: > W dniu 2012-10-04 20:51, Lev Serebryakov pisze: > > Hello, Marek. > > You wrote 3 октября 2012 г., 23:17:35: > > > >>> atrtc0: <AT realtime clock> port 0x70-0x71 on acpi0 > > MS> still the same in my environment, running FreeBSD 9.1 under ESXi5.1 host > > MS> Do you have any solution? > > In my case it was local patch for exotic embedded chipset... > Can you send me the patch so I can have a look if I don't use the same > chipset ? > > Regards, It is the patch attached to this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=170705 The patch fixes a problem with old AMD Geode chipsets, but causes a hang at atrtc attach when run under virtualbox, and I haven't had time yet to install and learn to use vbox enough to debug it. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1349383564.2363.111.camel>