Date: Thu, 17 Jun 2010 22:49:27 -0400 From: "Alexandre \"Sunny\" Kovalenko" <gaijin.k@ovi.com> To: Nenhum_de_Nos <matheus@eternamente.info> Cc: freebsd-stable@freebsd.org Subject: Re: kernel panic on 8.1-rc1 amd64 Message-ID: <1276829367.66339.25.camel@RabbitsDen> In-Reply-To: <c7ee7b72d6965f37817f11c1ee5b0712.squirrel@cygnus.homeunix.com> References: <5468c5ca1e5d48af91d88d39454d4f08.squirrel@cygnus.homeunix.com> <1276714128.78582.0.camel@RabbitsDen> <c357e8a1ef0b9fed7d02bb05d93ed38e.squirrel@cygnus.homeunix.com> <1276740032.66339.16.camel@RabbitsDen> <c7ee7b72d6965f37817f11c1ee5b0712.squirrel@cygnus.homeunix.com>
index | next in thread | previous in thread | raw e-mail
On Thu, 2010-06-17 at 17:12 -0300, Nenhum_de_Nos wrote: > On Wed, June 16, 2010 23:00, Alexandre \"Sunny\" Kovalenko wrote: > > On Wed, 2010-06-16 at 21:48 -0300, Nenhum_de_Nos wrote: > >> On Wed, June 16, 2010 15:48, Alexandre \"Sunny\" Kovalenko wrote: > >> > On Wed, 2010-06-16 at 12:59 -0300, Nenhum_de_Nos wrote: > >> >> hail, > >> >> > >> >> has anyone seen a panic right after kernel is loaded from beastie > >> screen > >> >> ? > >> >> > >> >> this is an Asus F3T running amd64 version. I had first problem when I > >> >> csuped to stable already in 8.1-prerelease time. I then got to boot > >> >> another kernel and csuped to releng_8_0 and all was ok again. now > >> that I > >> >> saw rc1 in cvsweb, I gave rc1 a try, and same problem. > >> >> > >> >> all I see is that message from kernel panic (that is followed by 15 > >> >> seconds to reboot or press a key) passing on screen one after the > >> other, > >> >> no time to read what it is. only key that works is power key, and > >> when > >> >> it > >> >> is pressed and hold, the messages stop to scroll and the last message > >> is > >> >> there for a really small fraction of time. > >> >> > >> >> I have no idea on how to get more info on this. > >> >> > >> >> thanks, > >> >> > >> >> matheus > >> >> > >> > > >> > Is it possible that you are loading VirtualBox modules from > >> loader.conf? > >> > >> very likely. I'll try to unload it from boor prompt later. > >> > >> thanks, > >> > >> matheus > >> > > > > You actually might want to 'disable' them from the boot prompt. > > did it, no good. though :( > > (I disabled vboxdrv.ko) > > any other ideas ? > > thanks, > > matheus > 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. -- Alexandre Kovalenko (Олександр Коваленко) -------------------------------------------------------------- Ovi Mail: Create an account directly from your phone http://mail.ovi.comhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1276829367.66339.25.camel>