From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Christopher S. Aker" <caker@theshore.net>
Subject: hypervisor crash when shutting down domU in tonight's
	-unstable
Date: Fri, 22 Apr 2005 00:45:16 -0500
Message-ID: <036601c546fe$78648be0$0201a8c0@hawk>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Latest -unstable, issuing xm shutdown results in the following crash.  I have a
suspicion it'ss related to "ChangeSet 1.1340.1.1":

> Patch to enable the destruction of domains which have shadow mode enabled.
> Also fixes some shadow mode ref counting bugs, and one bug in check_pte()
> recently introduced by the changes in page table accessor types/macros.

Fake shadow is off in my dom0 config.

Binaries: http://www.theshore.net/~caker/xen/BUGshutdown/

(XEN) CPU:    0
(XEN) EIP:    0808:[<ff125284>]
(XEN) EFLAGS: 00010246   CONTEXT: hypervisor
(XEN) eax: 00000000   ebx: 00000000   ecx: 00000000   edx: 00000000
(XEN) esi: 00000000   edi: ff1bea80   ebp: 00000000   esp: ff103e18
(XEN) ds: 0810   es: 0810   fs: 0810   gs: 0810   ss: 0810   cs: 0808
(XEN) Stack trace from ESP=ff103e18:
(XEN)    ff1bea80 00000002 00000296 00000000 fc411bf8 ffbf2900 00000000 00000000
(XEN)    00000000 ff1bea80 80000004 [ff117a62] ff1bea80 00000000 00000002 00000000
(XEN)    ff1bea80 00000000 00000002 [ff105707] ff1bea80 ff1bea80 ffbf0080 [ff104a90]
(XEN)    ff1bea80 bfffe3c0 00000030 00287000 0000882d 00000a18 c082da1c 00288000
(XEN)    c8a88000 00000000 000e0003 c014494c 00000061 00010246 c0037e2c 00000069
(XEN)    0000007b 0000007b 40000000 00000000 00000000 f0000000 40000000 80000004
(XEN)    00000246 0000d50a ffbf0080 [ff11cc47] 0934d000 a0000000 40000000 00000000
(XEN)    00000004 00000001 00008103 ffbf2900 08103000 08103030 [ff120b5e] fee44030
(XEN)    a0000000 c432be60 e0000000 [ff106a29] 80000003 ffbf2900 80000004 00000001
(XEN)    e0000000 fc513c58 ffbf2900 [ff11bced] fc513c58 e0000000 ff15be04 fe2df38c
(XEN)    0b7d9067 0b7d9065 ffbf2900 [ff11be99] 00000009 aaaa1004 00000002 b7f3ccc2
(XEN)    b74bd2d4 5b1f43e7 b7cf1680 b7fbc42c 00000000 b74bfbdc bfffe418 b7f3c921
(XEN)    ff15be00 00000000 00000000 ffbf0080 b7eb1331 5b1f43e7 c3544000 [ff1376a3]
(XEN)    bfffe3c0 0000007f bfffe3bc b7eb1331 5b1f43e7 c3544000 00000007 000e0007
(XEN)    c0255744 00000061 00000246 c3545d4c 00000069 0000007b 0000007b 00000000
(XEN)    00000033 ffbf0080
(XEN) Call Trace from ESP=ff103e18:
(XEN)    [<ff117a62>] [<ff105707>] [<ff104a90>] [<ff11cc47>] [<ff120b5e>]
[<ff106a29>]
(XEN)    [<ff11bced>] [<ff11be99>] [<ff1376a3>]

****************************************
CPU0 FATAL PAGE FAULT
[error_code=0000]
Faulting linear address might be 00000004
Aieee! CPU0 is toast...
****************************************

Reboot in five seconds...