Date: Sat, 30 Jun 2012 15:33:34 +0200 From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@FreeBSD.org> To: "Sean C. Farley" <scf@freebsd.org> Cc: freebsd-emulation@freebsd.org Subject: Re: VirtualBox 4.1.14 panic Message-ID: <CAE-m3X07j9RvZ=Fc28Su55H7YfA475W5sfKFK94OeE2Z%2BE=ujg@mail.gmail.com> In-Reply-To: <alpine.BSF.2.02.1205072203220.4028@thor.farley.org> References: <alpine.BSF.2.02.1205072203220.4028@thor.farley.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 8, 2012 at 4:25 AM, Sean C. Farley <scf@freebsd.org> wrote: > I experienced a panic while starting a new image using Vagrant[1]. Vagran= t > uses VBoxManage to do its work. =A0I was away from my system when it happ= ened, > so I do not know exactly at what point it occurred. > > This is the last bits of logging I had captured from Vagrant. Fortunately= , I > had that going for my own purposes (non-panic). =A0I am almost certain th= ere > is more past 30% but was not synced to disk. > > DEBUG virtualbox: Finding driver for VirtualBox version: 4.1.14 > =A0INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_= 4_1 > =A0INFO virtualbox_base: VBoxManage path: VBoxManage > =A0INFO vm: Loading guest: linux > =A0INFO warden: Calling action: > #<Vagrant::Action::VM::Import:0x000008032892a8> > =A0INFO interface: info: Importing base box 'centos-6.2-dev'... > [default] Importing base box 'centos-6.2-dev'... > =A0INFO subprocess: Starting process: ["VBoxManage", "import", > "/home/blah/.vagrant.d/boxes/centos-6.2-dev/box.ovf"] > DEBUG subprocess: Selecting on IO > DEBUG subprocess: stderr: Pseudo-terminal will not be allocated because > stdin is not a terminal. > > DEBUG subprocess: stderr: 0%... > DEBUG subprocess: stderr: > 10%...20%...30%...40%...50%...60%...70%...80%...90%...100% > Interpreting /home/blah/.vagrant.d/boxes/centos-6.2-dev/box.ovf... > OK. > 0%... > DEBUG subprocess: stderr: 10%... > =A0INFO interface: info: ^MESC[0K > [default] ^MESC[0K INFO interface: info: Progress: 10% > [default] Progress: 10%DEBUG subprocess: stderr: 20%... > =A0INFO interface: info: ^MESC[0K > [default] ^MESC[0K INFO interface: info: Progress: 20% > [default] Progress: 20%DEBUG subprocess: stderr: 30%... > =A0INFO interface: info: ^MESC[0K > [default] ^MESC[0K INFO interface: info: Progress: 30% > [default] Progress: 30% > > Now, for the good stuff. =A0Unfortunately, the panic was not written to d= isk > correctly, however, here is the bit I did find. =A0This looks similar to = the > panic Mikolaj reported[2], but mine appears to be on the shutdown of the > VM's network. =A0My host is 8.3-STABLE r235116 amd64 (Q6600) running with= 8GB > and the nVidia driver v295.40. =A0When I noticed the system had frozen (n= o > network either), the screensaver had been running. The screensaver does n= ot > use OpenGL out of (probably an old) paranoia that the system could panic > from VirtualBox and an OpenGL application running at the same time. =A0No > VIMAGE nor VLAN is involved. =A0The VM is using NAT. > > Fatal trap 12: page fault while in kernel mode > cpuid =3D 2; apic id =3D 02 > fault virtual address =A0 =3D 0x12 > fault code =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D supervisor read data, page not = present > instruction pointer =A0 =A0 =3D 0x20:0xffffffff81e26394 > stack pointer =A0 =A0 =A0 =A0 =A0 =3D 0x28:0xffffff824790e970 > frame pointer =A0 =A0 =A0 =A0 =A0 =3D 0x28:0xffffff824790e9a0 > code segment =A0 =A0 =A0 =A0 =A0 =A0=3D base 0x0, limit 0xfffff, type 0x1= b > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D DPL 0, pres 1, long 1,= def32 0, gran 1 > processor eflags =A0 =A0 =A0 =A0=3D interrupt enabled, resume, IOPL =3D 0 > current process =A0 =A0 =A0 =A0 =3D 23702 (initial thread) > trap number =A0 =A0 =A0 =A0 =A0 =A0 =3D 12 > panic: page fault > cpuid =3D 2 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > kdb_backtrace() at kdb_backtrace+0x37 > panic() at panic+0x187 > trap_fatal() at trap_fatal+0x290 > trap_pfault() at trap_pfault+0x23e > trap() at trap+0x3ce > calltrap() at calltrap+0x8 > --- trap 0xc, rip =3D 0xffffffff81e26394, rsp =3D 0xffffff824790e970, rbp= =3D > 0xffffff824790e9a0 --- > vboxNetAdpOsDestroy() at vboxNetAdpOsDestroy+0x14 > vboxNetAdpDestroy() at vboxNetAdpDestroy+0x2d > VBoxNetAdpFreeBSDCtrlioctl() at VBoxNetAdpFreeBSDCtrlioctl+0x60 > devfs_ioctl_f() at devfs_ioctl_f+0x7b > kern_ioctl() at kern_ioctl+0x102 > ioctl() at ioctl+0xfd > amd64_syscall() at amd64_syscall+0x1f4 > Xfast_syscall() at Xfast_syscall+0xfc > --- syscall (54, FreeBSD ELF64, ioctl), rip =3D 0x800c94bfc, rsp =3D > 0x7fffffffc2f8, rbp =3D 0x7fffffffc320 --- > Uptime: 8h31m17s > Dumping 1351 out of 8163 MB:..2%panic: bufwrite: buffer is not busy??? > cpuid =3D 2 > > Sean > =A01. http://vagrantup.com/ > =A02. > http://lists.freebsd.org/pipermail/freebsd-emulation/2012-April/009646.ht= ml This looks similar to the problem described in ports/169565. Could you plea= se try the described modification there and see if it helps? http://www.freebsd.org/cgi/query-pr.cgi?pr=3D169565 --=20 Bernhard Froehlich http://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-m3X07j9RvZ=Fc28Su55H7YfA475W5sfKFK94OeE2Z%2BE=ujg>