freebsd stable - Feb 2013 - 9-STABLE: bce pulse(): Warning: bootcode thinks driver is absent

I just started to try and get VirtualBox up and running on this server .. same
configuration as another server I already have a few of them running, but after
a period of time with the install, I get the above error pop up on my remote
console, and pinging to the server itself just dies ?

I'm up to date for src / 9-STABLE as of today ? have never seen this one
before, nor can I seem to find anything useful through google except for points
to the code itself ?

When it dies, it isn't just the network that is dead, but the whole machine
appears to be un-responsive ?

When I rebuilt the kernel, I did also rebuild VirtualBox/kmod, since I've
experienced odd things with it in the past ?

Anyone have any ideas on what is causing this?  Something with VirtualBox
triggering ? something?

Thx

Further to this ? I just did a 'ctl-alt-del' through my remote console,
which appears to have 'unstuck' whatever it was, in that I got a bunch
of Login: prompts scroll up the screen (hit return a few times after it got
stuck), after which it seems to do a full shutdown and reboot, as if nothing was
wrong ?

I had a ping process running against that machine, which halted ? but when I hit
ctl-alt-del, a whack of responses came back with really high times:

==64 bytes from 200.46.151.146: icmp_seq=3104 ttl=64 time=215390.333 ms
64 bytes from 200.46.151.146: icmp_seq=3105 ttl=64 time=214389.342 ms
64 bytes from 200.46.151.146: icmp_seq=3286 ttl=64 time=33295.200 ms
64 bytes from 200.46.151.146: icmp_seq=3287 ttl=64 time=32294.228 ms
64 bytes from 200.46.151.146: icmp_seq=3288 ttl=64 time=31296.220 ms
64 bytes from 200.46.151.146: icmp_seq=3289 ttl=64 time=30296.262 ms
<whack deleted>
64 bytes from 200.46.151.146: icmp_seq=3315 ttl=64 time=4299.235 ms
64 bytes from 200.46.151.146: icmp_seq=3316 ttl=64 time=3299.278 ms
64 bytes from 200.46.151.146: icmp_seq=3317 ttl=64 time=2298.324 ms
64 bytes from 200.46.151.146: icmp_seq=3318 ttl=64 time=1299.448 ms
64 bytes from 200.46.151.146: icmp_seq=3319 ttl=64 time=298.485 ms
64 bytes from 200.46.151.146: icmp_seq=3320 ttl=64 time=0.168 ms
64 bytes from 200.46.151.146: icmp_seq=3321 ttl=64 time=0.158 ms
64 bytes from 200.46.151.146: icmp_seq=3322 ttl=64 time=0.167 ms
64 bytes from 200.46.151.146: icmp_seq=3323 ttl=64 time=0.157 ms
<back to normal>
64 bytes from 200.46.151.146: icmp_seq=3330 ttl=64 time=0.137 ms
64 bytes from 200.46.151.146: icmp_seq=3331 ttl=64 time=0.159 ms
64 bytes from 200.46.151.146: icmp_seq=3332 ttl=64 time=0.154 ms
64 bytes from 200.46.151.146: icmp_seq=3333 ttl=64 time=0.204 ms
<no more ping response as server rebooting>


On 2013-02-24, at 12:22 AM, Marc Fournier <freebsd at hub.org> wrote:
> 
> I just started to try and get VirtualBox up and running on this server ..
same configuration as another server I already have a few of them running, but
after a period of time with the install, I get the above error pop up on my
remote console, and pinging to the server itself just dies ?
> 
> I'm up to date for src / 9-STABLE as of today ? have never seen this
one before, nor can I seem to find anything useful through google except for
points to the code itself ?
> 
> When it dies, it isn't just the network that is dead, but the whole
machine appears to be un-responsive ?
> 
> When I rebuilt the kernel, I did also rebuild VirtualBox/kmod, since
I've experienced odd things with it in the past ?
> 
> Anyone have any ideas on what is causing this?  Something with VirtualBox
triggering ? something?
> 
> Thx
> 
> 
> 
>