From owner-freebsd-stable@FreeBSD.ORG Fri Jun 18 20:10:45 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B13AD106566C for ; Fri, 18 Jun 2010 20:10:45 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (mail.farley.org [IPv6:2001:470:1f0f:20:2::11]) by mx1.freebsd.org (Postfix) with ESMTP id 500118FC12 for ; Fri, 18 Jun 2010 20:10:45 +0000 (UTC) Received: from thor.farley.org (HPooka@thor.farley.org [IPv6:2001:470:1f0f:20:1::5]) by mail.farley.org (8.14.4/8.14.4) with ESMTP id o5IKAYEP087362; Fri, 18 Jun 2010 15:10:34 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Fri, 18 Jun 2010 15:10:34 -0500 (CDT) From: "Sean C. Farley" To: Nenhum_de_Nos In-Reply-To: <30abfcea22fe676302cd91fcf3a41c3e.squirrel@lamneth> Message-ID: References: <5468c5ca1e5d48af91d88d39454d4f08.squirrel@cygnus.homeunix.com> <1276714128.78582.0.camel@RabbitsDen> <1276740032.66339.16.camel@RabbitsDen> <1276829367.66339.25.camel@RabbitsDen> <30abfcea22fe676302cd91fcf3a41c3e.squirrel@lamneth> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-1.4 required=4.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.farley.org Cc: freebsd-stable@FreeBSD.org Subject: Re: kernel panic on 8.1-rc1 amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 20:10:45 -0000 On Fri, 18 Jun 2010, Nenhum_de_Nos wrote: > On Thu, June 17, 2010 23:49, Alexandre \"Sunny\" Kovalenko wrote: >> Not much -- this is just panic I had in the same timeframe and solved >> it by disabling and, consequently rebuilding, Virtual Box kernel >> modules. I assume you either not loading or did disable the remaining >> two: vboxnetflt.ko and vboxnetadp.ko. >> >> I guess any third-party modules (webcam, qemu, etc.) would be good >> candidates for being disabled -- it seams like there were changes in >> the kernel which required rebuild of them. >> >> Outside of that -- sorry, out of ideas. > > thanks for the tip, for the record it was a module (or two), as I > tried disabling both nvidia and vboxdrv. > > I'll try to update both now, For the record, it has been reported on emulation@ that the nvidia and vbox drivers do not get along with each other. I occasionally get lockups while there is network traffic between my host and (console-only) guest both running FreeBSD 8 amd64. Unfortunately, I do not know which module is at fault, and I have been too busy to try harder to find the culprit. Sean -- scf@FreeBSD.org