Date: Thu, 4 Oct 2012 22:51:19 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: Marek Salwerowicz <marek_sal@wp.pl> 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: <13310645740.20121004225119@serebryakov.spb.ru> In-Reply-To: <506C8F4F.3040703@wp.pl> References: <80840563.20120920002200@serebryakov.spb.ru> <506C8F4F.3040703@wp.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Marek. You wrote 3 =EE=EA=F2=FF=E1=F0=FF 2012 =E3., 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... --=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?13310645740.20121004225119>