From owner-freebsd-stable@FreeBSD.ORG Sun Feb 24 08:22:20 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 69AF0172; Sun, 24 Feb 2013 08:22:20 +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 2C6F018BF; Sun, 24 Feb 2013 08:22:20 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.188]) by hub.org (Postfix) with ESMTP id A50E8221010; Sun, 24 Feb 2013 04:22:12 -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 14503-06; Sun, 24 Feb 2013 08:22:12 +0000 (UTC) Received: from [192.168.0.52] (S01067cb21b2ff4ca.gv.shawcable.net [24.108.26.71]) by hub.org (Postfix) with ESMTPA id 9822422100E; Sun, 24 Feb 2013 04:22:11 -0400 (AST) From: Marc Fournier Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: 9-STABLE: bce pulse(): Warning: bootcode thinks driver is absent Date: Sun, 24 Feb 2013 00:22:10 -0800 Message-Id: To: "freebsd-stable@freebsd.org" Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Feb 2013 08:22:20 -0000 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 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 When it dies, it isn't just the network that is dead, but the whole = machine appears to be un-responsive =85 When I rebuilt the kernel, I did also rebuild VirtualBox/kmod, since = I've experienced odd things with it in the past =85=20 Anyone have any ideas on what is causing this? Something with = VirtualBox triggering =85 something? Thx