From owner-freebsd-net@FreeBSD.ORG Sun Feb 24 08:26:48 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 365803FF; Sun, 24 Feb 2013 08:26:48 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.208.146]) by mx1.freebsd.org (Postfix) with ESMTP id C885418FE; Sun, 24 Feb 2013 08:26:47 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.188]) by hub.org (Postfix) with ESMTP id EEA91191CEAE; Sun, 24 Feb 2013 04:26:46 -0400 (AST) Received: from hub.org ([200.46.208.146]) by maia.hub.org (mx1.hub.org [200.46.151.188]) (amavisd-maia, port 10024) with ESMTP id 16009-01; Sun, 24 Feb 2013 08:26:46 +0000 (UTC) Received: from [192.168.0.52] (S01067cb21b2ff4ca.gv.shawcable.net [24.108.26.71]) by hub.org (Postfix) with ESMTPA id DBBB1191CEAD; Sun, 24 Feb 2013 04:26:45 -0400 (AST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: 9-STABLE: bce pulse(): Warning: bootcode thinks driver is absent From: Marc Fournier In-Reply-To: Date: Sun, 24 Feb 2013 00:26:43 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "freebsd-stable@freebsd.org" X-Mailer: Apple Mail (2.1499) Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Feb 2013 08:26:48 -0000 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 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 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 On 2013-02-24, at 12:22 AM, Marc Fournier 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