Date: Sun, 24 Feb 2013 00:26:43 -0800 From: Marc Fournier <freebsd@hub.org> To: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: 9-STABLE: bce pulse(): Warning: bootcode thinks driver is absent Message-ID: <C59CD28C-BC78-4C51-A1AF-4C58253E6F1A@hub.org> In-Reply-To: <DC287D7D-7383-4D19-BA0E-3A8237BFA8C1@hub.org> References: <DC287D7D-7383-4D19-BA0E-3A8237BFA8C1@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Further to this =85 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 =85 I had a ping process running against that machine, which halted =85 but = when I hit ctl-alt-del, a whack of responses came back with really high = times: =3D=3D=3D 64 bytes from 200.46.151.146: icmp_seq=3D3104 ttl=3D64 time=3D215390.333 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3105 ttl=3D64 time=3D214389.342 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3286 ttl=3D64 time=3D33295.200 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3287 ttl=3D64 time=3D32294.228 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3288 ttl=3D64 time=3D31296.220 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3289 ttl=3D64 time=3D30296.262 = ms <whack deleted> 64 bytes from 200.46.151.146: icmp_seq=3D3315 ttl=3D64 time=3D4299.235 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3316 ttl=3D64 time=3D3299.278 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3317 ttl=3D64 time=3D2298.324 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3318 ttl=3D64 time=3D1299.448 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3319 ttl=3D64 time=3D298.485 ms 64 bytes from 200.46.151.146: icmp_seq=3D3320 ttl=3D64 time=3D0.168 ms 64 bytes from 200.46.151.146: icmp_seq=3D3321 ttl=3D64 time=3D0.158 ms 64 bytes from 200.46.151.146: icmp_seq=3D3322 ttl=3D64 time=3D0.167 ms 64 bytes from 200.46.151.146: icmp_seq=3D3323 ttl=3D64 time=3D0.157 ms <back to normal> 64 bytes from 200.46.151.146: icmp_seq=3D3330 ttl=3D64 time=3D0.137 ms 64 bytes from 200.46.151.146: icmp_seq=3D3331 ttl=3D64 time=3D0.159 ms 64 bytes from 200.46.151.146: icmp_seq=3D3332 ttl=3D64 time=3D0.154 ms 64 bytes from 200.46.151.146: icmp_seq=3D3333 ttl=3D64 time=3D0.204 ms <no more ping response as server rebooting> On 2013-02-24, at 12:22 AM, Marc Fournier <freebsd@hub.org> wrote: >=20 > 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 =85 >=20 > I'm up to date for src / 9-STABLE as of today =85 have never seen this = one before, nor can I seem to find anything useful through google except = for points to the code itself =85 >=20 > When it dies, it isn't just the network that is dead, but the whole = machine appears to be un-responsive =85 >=20 > When I rebuilt the kernel, I did also rebuild VirtualBox/kmod, since = I've experienced odd things with it in the past =85=20 >=20 > Anyone have any ideas on what is causing this? Something with = VirtualBox triggering =85 something? >=20 > Thx >=20 >=20 >=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C59CD28C-BC78-4C51-A1AF-4C58253E6F1A>