The following reply was made to PR kern/186051; it has been noted by GNATS.
From: Steven Spence <free...@stratum16.com>
To: John Baldwin <j...@freebsd.org>
Cc: bug-follo...@freebsd.org
Subject: Re: kern/186051: [vmware] [panic] FreeBSD 8.4+, 9.x+, 10.0 guest
panic with VMWare Server on boot
Date: Mon, 28 Apr 2014 21:04:40 -0600
This is a multi-part message in MIME format.
--------------020308050805030308030905
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 04/28/2014 08:32 AM, John Baldwin wrote:
>
> On Monday, April 21, 2014 01:45:10 PM Steven Spence wrote:
>
> > Output of "sysctl machdep.idle"
>
> >
>
> > machdep.idle: amdc1e
>
> >
>
> > This is from a 8.3-RELEASE-p15 box.
>
> Hummm. We really shouldn't be doing anything differently. However, we do a
>
> bit more (including a wrmsr) during idle halt on your machine. Can you
> build
>
> a stable/8 kernel with debug symbols in an 8.3 guest and capture the panic
>
> messages from booting that kernel?
>
>
Here is a capture of the panic from a stable/8 kernel. Is the only
debugging option you are looking for in the kernel config
"makeoptions DEBUG=-g"? I still have the 8.3 kernel on there I can
boot if I need to get in and recompile the stable/8 kernel differently.
I am not sure how much use the information below will be to you.
kernel trap 1 with interrupts disabled
Fatal trap 1: privileged instruction fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer = 0x20:0xffffffff809c342e
stack pointer = 0x28:0xffffff8000211b40
acd0: CDROM <VMware Virtual IDE CDROM Drive/00000001> at ata1-master UDMA33
frame pointer = 0x28:0xffffff8000211b60
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = resume, IOPL = 0
current process = 11 (idle: cpu0)
trap number = 1
panic: privileged instruction fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff8067c0b6 at kdb_backtrace+0x66
#1 0xffffffff8064861e at panic+0x1ce
#2 0xffffffff809d3750 at trap_fatal+0x290
#3 0xffffffff809d3ce5 at trap+0x105
#4 0xffffffff809ba944 at calltrap+0x8
#5 0xffffffff8066e08f at sched_idletd+0x11f
#6 0xffffffff8061ceaf at fork_exit+0x11f
#7 0xffffffff809bae8e at fork_trampoline+0xe
Uptime: 1s
Cannot dump. Device not defined or unavailable.
Automatic reboot in 15 seconds - press a key on the console to abort
I have also tried to dump the panic to a swap device but I don't think
it is getting far enough in the kernel boot to initialize any hard drive
storage devices.
If there is anything else I can try to get more information out of this
let me know.
Thanks,
Steven
--------------020308050805030308030905
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 04/28/2014 08:32 AM, John Baldwin
wrote:<br>
</div>
<blockquote cite="mid:6420631.eccgv7r...@ralph.baldwin.cx"
type="cite">
<meta name="qrichtext" content="1">
<style type="text/css">
p, li { white-space: pre-wrap; }
</style>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">On Monday, April 21, 2014 01:45:10 PM Steven
Spence wrote:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">> Output of "sysctl machdep.idle"</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">> </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">> machdep.idle: amdc1e</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">> </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">> This is from a 8.3-RELEASE-p15 box.</p>
<p style="-qt-paragraph-type:empty; margin-top:0px;
margin-bottom:0px; margin-left:0px; margin-right:0px;
-qt-block-indent:0; text-indent:0px; "> </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">Hummm. We really shouldn't be doing anything
differently. However, we do a</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">bit more (including a wrmsr) during idle halt
on your machine. Can you build</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">a stable/8 kernel with debug symbols in an
8.3 guest and capture the panic</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">messages from booting that kernel?</p>
<br>
</blockquote>
<br>
Here is a capture of the panic from a stable/8 kernel. Is the only
debugging option you are looking for in the kernel config
"makeoptions DEBUG=-g"? I still have the 8.3
kernel on there I
can boot if I need to get in and recompile the stable/8 kernel
differently. I am not sure how much use the information below will
be to you.<br>
<br>
kernel trap 1 with interrupts disabled<br>
Fatal trap 1: privileged instruction fault while in kernel mode<br>
cpuid = 0; apic id = 00<br>
instruction pointer = 0x20:0xffffffff809c342e<br>
stack pointer
= 0x28:0xffffff8000211b40<br>
acd0: CDROM <VMware Virtual IDE CDROM Drive/00000001> at
ata1-master UDMA33 <br>
frame pointer
= 0x28:0xffffff8000211b60<br>
code
segment =
base 0x0, limit 0xfffff, type 0x1b<br>
= DPL 0, pres 1, long 1, def32 0, gran 1<br>
processor eflags = resume, IOPL
= 0<br>
current process = 11
(idle: cpu0)<br>
trap
number
= 1<br>
panic: privileged instruction fault<br>
cpuid = 0<br>
KDB: stack backtrace:<br>
#0 0xffffffff8067c0b6 at kdb_backtrace+0x66<br>
#1 0xffffffff8064861e at panic+0x1ce<br>
#2 0xffffffff809d3750 at trap_fatal+0x290<br>
#3 0xffffffff809d3ce5 at trap+0x105<br>
#4 0xffffffff809ba944 at calltrap+0x8<br>
#5 0xffffffff8066e08f at sched_idletd+0x11f<br>
#6 0xffffffff8061ceaf at fork_exit+0x11f<br>
#7 0xffffffff809bae8e at fork_trampoline+0xe<br>
Uptime: 1s<br>
Cannot dump. Device not defined or unavailable.<br>
Automatic reboot in 15 seconds - press a key on the console to abort<br>
<br>
I have also tried to dump the panic to a swap device but I don't
think it is getting far enough in the kernel boot to initialize any
hard drive storage devices.<br>
<br>
If there is anything else I can try to get more information out of
this let me know.<br>
<br>
Thanks,<br>
Steven<br>
</body>
</html>
--------------020308050805030308030905--
_______________________________________________
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
