6.0-beta1 panics in vmware5 while installing
Julian Elischer
julian at elischer.org
Mon Jul 25 04:31:03 GMT 2005
Giovanni P. Tirloni wrote:
> Hi,
>
> I really don't know if this is a Vmware or FreeBSD problem but since
> 4.11 and 5.4 worked on Vmware 5.0 I'm reporting this panic. The
> virtual machine has 128MB, 6GB disk and one network card (no usb or
> floppy).
>
> It happens while installing. In the debug console the last two
> messages are:
>
> DEBUG: Generating /etc/fstab file
> DEBUG: CD Volume 1 initialized!
>
> Then it panics with the following message:
>
> panic: duplicate free of item 0xc1854738 from zone 0xc144adc0(g_bio)
>
> cpuid = 0
> KDB: enter: panic
> [thread pid 3 tid 100034]
> Stopped at kdb_enter+0x2b: nop
> db> trace
> Tracing pid 3 tid 100034 td 0xc16df600
> kdb_enter(c0854b84) at kdb_enter+0x2b
> panic(c086f563,c1854738,c144adc0,c084f668,c086f547) at panic+0x127
> uma_dbg_free
> uma_zfree_arg
> g_destroy_bio
> g_vfs_done
> biodone
> g_io_schedule_up
> g_up_procbody
> fork_exit
> fork_trampoline
> --- trap 0x1, eip = 0, esp = 0xc7b81d6c, ebp = 0 ---
>
> pid 3 is [CPU 0] g_up
>
> Is there a easier way to copy the console info ? network kdb perhaps ?
boot the vm with
console="comconsole" in /boot/loader.conf
typing "set console=comconsole" at the boot prompt
and in the base machine connect the outgoing data from the emulated com1
to somewhere you can get to it..
you can hook it to a pty or /dev/nmdm0 (nullmodem) on FreeBSD but I don't
know how one would do it on other OSs.
>
> Thank you,
>
More information about the freebsd-current
mailing list