From: Micah Anderson <micah@riseup.net>
To: xen-devel@lists.xensource.com
Subject: domU crashing, trying to determine why
Date: Sat, 01 Jan 2011 14:16:55 -0500 [thread overview]
Message-ID: <87mxnka0yg.fsf@algae.riseup.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2234 bytes --]
I'm having a domU that is regularly crashing, without any obvious reason
why. I set 'on_crash=preserve' to try and get a crash to try and get
some clues, but what I got doesn't too obvious to me. I was hoping
someone here would be able to give me some clues.
Thanks for any clues anyone can give! Here is what I managed to eke out:
root@guillemot:/etc/xen# /usr/lib/xen-3.2-1/bin/xenctx -s /boot/System.map-2.6.26-2-xen-686 11 0
eip: c01013a7 hypercall_page+0x3a7 flags: 00001246 i z p
esp: c0389fbc
eax: 00000000 ebx: 00000001 ecx: 00000000 edx: c0389fc8
esi: 00000000 edi: 00000000 ebp: 00000000
cs: 00000061 ds: 0000007b fs: 000000d8 gs: 00000000
Stack:
c0105f52 ffffffff 00000000 c06ca9dd 0009cf8a 00000000 00000020 ffffffff
c01028ab c0102810 00000020 c1631000 00000000 c038f88b c03ac580 0702080b
00000000
Code:
cc cc cc cc cc cc cc cc cc cc cc cc cc cc b8 1d 00 00 00 cd 82 <c3> cc cc cc cc cc cc cc cc cc cc
Call Trace:
[<c01013a7>] hypercall_page+0x3a7 <--
[<c0105f52>] xen_safe_halt+0x9f
[<c01028ab>] xen_idle+0x1b
[<c0102810>] cpu_idle+0xa8
[<c038f88b>] start_kernel+0x2f5
root@guillemot:/etc/xen# /usr/lib/xen-3.2-1/bin/xenctx -s /boot/System.map-2.6.26-2-xen-686 11 1
eip: c0170f39 file_kill+0x27 flags: 00001202 i nz
esp: e74cbf2c
eax: ec825e98 ebx: d7033a80 ecx: ee07207f edx: e7672e80
esi: d7033a80 edi: ed3942c0 ebp: ed396be8
cs: 00000061 ds: 0000007b fs: 000000d8 gs: 00000000
Stack:
00000010 c01710ae ed420f00 e81b3a78 e82d5cfc e7218b00 e74ca000 c016080d
c123f020 e81b3a78 c01608e7 000001e8 c123f020 e7218b00 e7218b4c 00000000
c011c723 00000000 e59bba80 c01214aa 00000001 e7447a80 e7688580 00000000
e76885c0 00000000 ed4ebd00 00000000 e74ca000 c0121998 00000000 00000000
Code:
13 8b 43 04 89 42 04 89 10 89 5b 04 89 1b f0 fe 05 40 42 38 c0 <0f> b7 15 40 42 38 c0 38 f2 0f 95
Call Trace:
[<c0170f39>] file_kill+0x27 <--
[<c01710ae>] __fput+0xd2
[<c016080d>] remove_vma+0x25
[<c01608e7>] exit_mmap+0xbc
[<c011c723>] mmput+0x24
[<c01214aa>] do_exit+0x1ad
[<c0121998>] do_group_exit+0x94
[<c01219ce>] sys_exit_group+0xd
[<c0103f76>] syscall_call+0x7
[<c02c0000>] zone_wait_table_init+0x47
[-- Attachment #1.2: Type: application/pgp-signature, Size: 835 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:[~2011-01-01 19:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 19:16 Micah Anderson [this message]
2011-01-01 21:41 ` domU crashing, trying to determine why Pasi Kärkkäinen
2011-01-02 0:43 ` micah anderson
2011-01-02 12:59 ` Pasi Kärkkäinen
2011-01-02 18:15 ` micah anderson
2011-01-02 18:39 ` Pasi Kärkkäinen
2011-01-03 3:41 ` micah anderson
2011-01-03 5:34 ` Pasi Kärkkäinen
2011-01-03 6:32 ` micah anderson
2011-01-03 16:40 ` Konrad Rzeszutek Wilk
2011-01-03 17:03 ` micah anderson
2011-01-03 17:14 ` Konrad Rzeszutek Wilk
2011-01-14 17:31 ` micah anderson
2011-01-14 17:45 ` Konrad Rzeszutek Wilk
2011-01-04 10:54 ` Ian Campbell
2011-01-04 19:49 ` micah anderson
2011-01-05 13:27 ` Ian Campbell
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=87mxnka0yg.fsf@algae.riseup.net \
--to=micah@riseup.net \
--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.