Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: virtualbox-ose 3.1.2 and 7.3-PRERELEASE

1 view
Skip to first unread message

{BBLister}

unread,
Feb 12, 2010, 6:20:29 AM2/12/10
to

> Hi there
>
> 02/02/2010 I had update my workstation from 7.2-STABLE to
> 7.3-PRERELEASE. After install new kernel and world all installed ports
> also was rebuilt too by portupgrade -af. Now, I have kernel panic
> during attempt starts any virtual machine (Win or BSD) via GUI or
> headless.
>
> Any suggestions are welcome.
>
> Thanks.
>
>
> Details:
>
>
>I've got additional info with last panic:
>
>Unread portion of the kernel message buffer:
>HHWWAACCCCMMRR00IInniittCCPPUU ccppuu 01
>
>HWACCMR0InitCPU failed with rc=-4013
>panic: vm_fault: fault on nofault entry, addr: c19ee000
>cpuid = 0
>Uptime: 28m29s
>Physical memory: 2026 MB
>Dumping 108 MB: 93 77 61 45 29 13


Hi,

I can confirm this.
When I upgraded to 7.3-PRELEASE and virtualbox-ose 3.1.2
I couldn't start ANY virtualbox machine, but immediately (in couple of secs)
my system panic.

I Upgraded to 8.0-STABLE and still my machine panics with virtualbox-ose 3.1.2

I upgraded to 8.0-STABLE with Virtualbox-ose-devel (3.1.5) and I still have panics.

I downgraded port to virtualbox-3.0.51.r22902_3 and still my 8.0-STABLE
machine immediatelly panics.


Note that in 7.2-STABLE my virtualbox-3.0.51.r22902_3 run without any problem
with many months uptime.

How can I find out what were the changes from 7.2-STABLE to 7.3-PRELEASE ?


I have an "AMD Athlon(tm) Processor (1394.08-MHz 686-class CPU)"

I always use the VBoxHeadless (no output on screen).

my dmesg follows:

Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.0-STABLE #1: Thu Feb 11 10:56:50 EET 2010
ro...@bigb4.homeftp.net:/usr/obj/usr/src/sys/bigb4 i386
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) Processor (1394.08-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x644 Stepping = 4
Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,
PAT,PSE36,MMX,FXSR>
AMD Features=0xc0440800<SYSCALL,<b18>,MMX+,3DNow!+,3DNow!>
real memory = 1073741824 (1024 MB)
avail memory = 1041551360 (993 MB)
acpi0: <AMIINT AMIINT10> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
vgapci0: <VGA-compatible display> mem 0xce000000-0xceffffff,0xc0000000-0xc7fff
fff irq 5 at device 0.0 on pci1
isab0: <PCI-ISA bridge> at device 2.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, USB> at device 2.2 (no driver attached)
pci0: <serial bus, USB> at device 2.3 (no driver attached)
atapci0: <SiS 735 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 2.5 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pci0: <multimedia, audio> at device 2.7 (no driver attached)
em0: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0xd400-0xd43f mem 0xcffa0000-0xcffbffff,0xcff80000-0xcff9ffff irq 5 at device 15.0 on pci0
em0: [FILTER]
em0: Ethernet address: 00:1b:21:17:0a:24
acpi_button0: <Sleep Button> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
cpu0: <ACPI CPU> on acpi0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcb7ff,0xcb800-0xcc7ff pnpid ORM0000 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
uart0: [FILTER]
uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
uart1: [FILTER]
Timecounter "TSC" frequency 1394075922 Hz quality 800
Timecounters tick every 1.000 msec
ipfw2 initialized, divert loadable, nat loadable, rule-based forwarding enabled, default to accept, logging disabled
ad0: 38166MB <Maxtor 5T040H4 TAH71DP0> at ata0-master UDMA100
GEOM: ad0: partition 1 does not ad1: 156334MB <Maxtor 6Y160P0 YAR41BW0> at ata0-slave UDMA100
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
cpu0: <ACPI CPU> on acpi0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcb7ff,0xcb800-0xcc7ff pnpid ORM0000 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
uart0: [FILTER]
uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
uart1: [FILTER]
Timecounter "TSC" frequency 1394075922 Hz quality 800
Timecounters tick every 1.000 msec
ipfw2 initialized, divert loadable, nat loadable, rule-based forwarding enabled, default to accept, logging disabled
ad0: 38166MB <Maxtor 5T040H4 TAH71DP0> at ata0-master UDMA100
GEOM: ad0: partition 1 does not ad1: 156334MB <Maxtor 6Y160P0 YAR41BW0> at ata0-slave UDMA100
start on a track boundary.
GEOM: ad0: partition 1 does not end on a track boundary.
GEOM: ad0s1: geometry does not match label (255h,63s != 16h,255s).
GEOM: ad1: partition 1 does not start on a track boundary.
GEOM: ad1: partition 1 does not end on a track boundary.
GEOM: ad1s1: geometry does not match label (255h,63s != 15h,255s).
Trying to mount root from ufs:/dev/ad0s1a

_______________________________________________
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulat...@freebsd.org"

Bernhard Froehlich

unread,
Feb 12, 2010, 6:53:48 AM2/12/10
to

Could you check out 8-stable at a specific date to narrow down what merge
causes this problems? At home i use 8-stable from about a month ago and
could not reproduce that so it should have happened in the last few weeks.

So if you do not want to test that but only have virtualbox working again
then try to check out the sources from about a month ago.

Thanks!

--
Bernhard Fröhlich
http://www.bluelife.at/

{BBLister}

unread,
Feb 12, 2010, 12:51:57 PM2/12/10
to
> Bernhard Fr??hlich
> http://www.bluelife.at/


Hi,

I can check out a previous 8-stable version.
A) If I use the following lines in my cvsup will this be ok? I will check out
8-stable of 10th of January 2010 of 01:01:01
( date=[cc]yy.mm.dd.hh.mm.ss )

===

*default release=cvs tag=RELENG_8
*default date=2010.01.10.01.01.01

===


B) What CPU do you have? Perhaps my AMD Athlon excibits the same behaviour
like AMD64 ? I see in wiki
"Launching virtual machine on 8.0-BETA2/amd64 instantly panic the system"

Thank you,

BB

Bernhard Froehlich

unread,
Feb 13, 2010, 9:48:19 AM2/13/10
to

Yeah looks good. I have checked my laptop and have:

FreeBSD 8.0-STABLE/amd64 #0: Fri Jan 8 09:39:23 CET 2010


> B) What CPU do you have? Perhaps my AMD Athlon excibits the same
behaviour
> like AMD64 ? I see in wiki
> "Launching virtual machine on 8.0-BETA2/amd64 instantly panic the
system"

CPU: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz (2194.52-MHz K8-class
CPU)

The panic mentioned above was already solved before 8.0-RELEASE.


--
Bernhard Fröhlich
http://www.bluelife.at/

{BBLister}

unread,
Feb 13, 2010, 11:33:24 AM2/13/10
to

Using the cvsup with entries

*default release=cvs tag=RELENG_8
*default date=2010.01.08.01.01.01


I cvsup and rebuild: (a) the kernel and (b) the virtualbox-ose-kmod for 3.1.2
Virtualbox was able to run succesfully with no panic (at least for 5 minutes..then I closed it
and continue with next experiment).

Now I moved a bit forward (10 days) on my cvsup and I am using

*default release=cvs tag=RELENG_8
*default date=2010.01.18.01.01.01

I will buildkernel and virtualbox-ose-kmod and test.

I will report on my findings. Anything else to test as I am doing this?
Is testing in periods of 10 days suggested or should I use different time windows?

BB

{BBLister}

unread,
Feb 14, 2010, 4:04:16 AM2/14/10
to


More on my tests:

After permorming a number of tests I found out that this strange bug was
fixed somehow during the last days. I have checked until
2010.02.07.01.01.01 (7th of February 2010) and there was no panic.
I then checked latest CVSUP (14th February 2010) and the panic had
dissapeared. Thus, I can conclude that a fix was made to address this problem
and now I have:

virtualbox-ose-vnc (3.1.2) execute succesfully on my 8.0-STABLE (with
cvsup 14th February 2010).

My tests were performed by compiling the kernel and virtualbox kernel module.

Because, all is normal now I will not continue the task to locate exactly what
went wrong during that period.

Thanks for the help,

Enrico M.

unread,
Feb 20, 2010, 3:26:52 PM2/20/10
to

Hi there,
I've got the same problem with my Athlon xp barton and 2Gb of ram, FreeBSD 8
Stable and ZFS
I updated src with cvsup 17th February 2010, but my system panics again.
Tomorrow, I'll try to go back at 8th January 2010.
Any suggestions are welcome
Thans in advance
Enrico M.

0 new messages