Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-10-04 Thread Lev Serebryakov
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... -- // Black Lion AKA

Re: [SPAM]Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-10-04 Thread Marek Salwerowicz
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

Re: [SPAM]Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-10-04 Thread Ian Lepore
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

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-10-03 Thread Marek Salwerowicz
W dniu 2012-09-19 22:22, Lev Serebryakov pisze: Hello, Freebsd-current. I've upgraded my FreeBSD-CURRENT Virtual machine, which I use to build router's NanoBSD image, to today's morning (MSK time, GMT+4) revision. Unfortunately, I cannot provide exact version, as sources are in this

Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Lev Serebryakov
Hello, Freebsd-current. I've upgraded my FreeBSD-CURRENT Virtual machine, which I use to build router's NanoBSD image, to today's morning (MSK time, GMT+4) revision. Unfortunately, I cannot provide exact version, as sources are in this unbootable VM too :) Kernel is GENERIC. VBox

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Lev Serebryakov
Hello, Freebsd-current. You wrote 20 сентября 2012 г., 0:22:00: LS I've upgraded my FreeBSD-CURRENT Virtual machine, which I use to LS build router's NanoBSD image, to today's morning (MSK time, GMT+4) LS revision. Unfortunately, I cannot provide exact version, as sources LS are in this

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Adrian Chadd
240689 is a doc commit. Which commit is it really? :) Adrian On 19 September 2012 13:37, Lev Serebryakov l...@freebsd.org wrote: Hello, Freebsd-current. You wrote 20 сентября 2012 г., 0:22:00: LS I've upgraded my FreeBSD-CURRENT Virtual machine, which I use to LS build router's

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Lev Serebryakov
Hello, Adrian. You wrote 20 сентября 2012 г., 0:41:20: It looks like patch to RTC which is useful on Geode LX causes this hang. AC 240689 is a doc commit. Which commit is it really? :) I'm testing theory (build kernel from fresh sources), that it is caused by local RTC patch, which helps

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Ian Lepore
On Thu, 2012-09-20 at 00:37 +0400, Lev Serebryakov wrote: Hello, Freebsd-current. You wrote 20 сентября 2012 г., 0:22:00: LS I've upgraded my FreeBSD-CURRENT Virtual machine, which I use to LS build router's NanoBSD image, to today's morning (MSK time, GMT+4) LS revision. Unfortunately,

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Adrian Chadd
Ah, what's the patch? adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Lev Serebryakov
Hello, Ian. You wrote 20 сентября 2012 г., 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

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Adrian Chadd
On 19 September 2012 13:54, Lev Serebryakov l...@freebsd.org wrote: Hello, Ian. You wrote 20 сентября 2012 г., 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

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Ian Lepore
On Wed, 2012-09-19 at 14:00 -0700, Adrian Chadd wrote: On 19 September 2012 13:54, Lev Serebryakov l...@freebsd.org wrote: Hello, Ian. You wrote 20 сентября 2012 г., 0:46:24: IL Yes, exactly. I updated the PR to request that my patch not get IL committed because it locks up virtualbox.

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Adrian Chadd
On 19 September 2012 14:05, Ian Lepore free...@damnhippie.dyndns.org wrote: 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? That should set the interrupt rate

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Ian Lepore
On Wed, 2012-09-19 at 14:08 -0700, Adrian Chadd wrote: On 19 September 2012 14:05, Ian Lepore free...@damnhippie.dyndns.org wrote: 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

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Adrian Chadd
On 19 September 2012 14:12, Ian Lepore free...@damnhippie.dyndns.org wrote: Right. Being totally clueless, is atrc_start() called just at probe/attach, or during normal operation? It's called just once, from the attach() routine for the rtc device. Right. Just have it loop over say 100

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Ian Lepore
On Wed, 2012-09-19 at 14:30 -0700, Adrian Chadd wrote: On 19 September 2012 14:12, Ian Lepore free...@damnhippie.dyndns.org wrote: Right. Being totally clueless, is atrc_start() called just at probe/attach, or during normal operation? It's called just once, from the attach() routine

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Garrett Cooper
On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore free...@damnhippie.dyndns.org wrote: ... Yes, exactly. I updated the PR to request that my patch not get committed because it locks up virtualbox. I hope to find time soon to learn enough about installing/configuring virtualbox to figure out what

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Adrian Chadd
On 19 September 2012 14:57, Garrett Cooper yaneg...@gmail.com wrote: On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore free...@damnhippie.dyndns.org wrote: ... Yes, exactly. I updated the PR to request that my patch not get committed because it locks up virtualbox. I hope to find time soon to

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Ian Lepore
On Wed, 2012-09-19 at 15:10 -0700, Adrian Chadd wrote: On 19 September 2012 14:57, Garrett Cooper yaneg...@gmail.com wrote: On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore free...@damnhippie.dyndns.org wrote: ... Yes, exactly. I updated the PR to request that my patch not get committed

Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

2012-09-19 Thread Yuri Pankov
On Wed, 19 Sep 2012 14:57:30 -0700, Garrett Cooper wrote: On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore free...@damnhippie.dyndns.org wrote: ... Yes, exactly. I updated the PR to request that my patch not get committed because it locks up virtualbox. I hope to find time soon to learn enough