From: Paul Larson <pl@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: xenstore test crash
Date: Thu, 09 Jun 2005 15:12:07 -0500 [thread overview]
Message-ID: <1118347928.2404.248.camel@localhost.localdomain> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2451 bytes --]
This has been opened as bug #74
(http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=74).
I tried running 'xs_test' with 'dir /' and it worked fine. However,
when I run xs_test --readonly and give it the 'dir /' command, the
system crashes and I get this:
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) CPU: 0
(XEN) EIP: 0073:[<00000000>]
(XEN) EFLAGS: 00010206 CONTEXT: guest
(XEN) eax: 00000000 ebx: 4017efec ecx: 080562f4 edx: 080564c4
(XEN) esi: 400162e0 edi: bffff4b4 ebp: bffff228 esp: bffff1fc
(XEN) cr0: 8005003b cr3: 18c80000
(XEN) ds: 007b es: 007b fs: 0000 gs: 0069 ss: 007b cs: 0073
(XEN) Guest stack trace from esp=bffff1fc:
(XEN) 080495fa 080562f4 080564cc 00000008 0804c4f1 08056294 080562f4
08051090(XEN) 080564c4 080562f4 4017efec bffff248 0804b9cc 080562f4 400162e0
bffff4b4(XEN) 0804c28d 0000000c bffff350 bffff468 0804c3ea 080562f4 08056294
bffff468(XEN) 0804c421 00000000 00000000 00000000 00000000 00000000 00000000
0000004e(XEN) 080562f4 00000000 00000000 00000000 00000000 00000000 00000000
00000000(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000(XEN) 080562f4 00000000 00000001 400166e0 00000054 00000800 00000000
00000000(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000(XEN) 00000000 00000000 00000000 00000000 00000000 762f0001 722f7261
782f6e75(XEN) 74736e65 6465726f 636f732f 5f74656b 40006f72 40017498 00000000
400cffde(XEN) 4017efec 4017ef84 bffff414 400854e5 4017efec bffff4c0 bffff434
4003f41a(XEN) 400166e0 40017218 400166e0 00000001 40016938 00000000 08051340
bffff448(XEN) 08048f7d 00000001 00000001 0000000a 0000000b 00000009 080560f4
080560c4(XEN) ffffffff 400162e0 bffff4b4 bffff488 400856c2 00000002 bffff4b4
bffff4c0\uffff\uffffEN) Domain 0 shutdown: rebooting machine.
--
Thanks,
Paul Larson
pl@us.ibm.com
IBM Linux Technology Center
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2005-06-09 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 20:12 Paul Larson [this message]
2005-06-10 0:15 ` xenstore test crash Rusty Russell
2005-06-10 3:21 ` Paul Larson
2005-06-10 14:27 ` Rusty Russell
2005-06-10 15:23 ` Keir Fraser
2005-06-12 6:57 ` Rusty Russell
2005-06-12 8:10 ` Vincent Hanquez
-- strict thread matches above, loose matches on Subject: below --
2005-06-12 8:38 Ian Pratt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1118347928.2404.248.camel@localhost.localdomain \
--to=pl@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.