From: Rik van Riel <riel@redhat.com>
To: Rik van Riel <riel@redhat.com>
Cc: xen-devel@lists.xensource.com, jun.nakajima@intel.com
Subject: Re: BUG: x86-64 VT crash backtrace
Date: Tue, 25 Jul 2006 12:55:53 -0400 [thread overview]
Message-ID: <44C64D19.7020002@redhat.com> (raw)
In-Reply-To: <44C6408E.4070700@redhat.com>
Rik van Riel wrote:
> here is the x86-64 VT crash backtrace, as promised. I can trigger it
> within minutes by simply starting up a 64 bit VT domain on a 64 bit system.
And another, more creative one. It seems to have bitmap_subset
in common with the first backtrace, and the assertion looks like
it could be a useful hint:
(XEN) (file=extable.c, line=77) Pre-exception: ffff830000153d1d ->
0000000000000000
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e010:[<ffff830000153d1d>] bitmap_subset+0x30/0x9d
(XEN) RFLAGS: 0000000000010046 CONTEXT: hypervisor
(XEN) rax: fffffffffffffffc rbx: ffff8300002230b8 rcx: 0000000000000000
(XEN) rdx: 0000000000000002 rsi: ffff83000024db08 rdi: ffff830000223060
(XEN) rbp: ffff830000223018 rsp: ffff830000222fe8 r8: 0000000000000000
(XEN) r9: 70202020200a0a3b r10: 542e2220746e6972 r11: 6d202020200a3b29
(XEN) r12: ffffffff804bc220 r13: 000001000d3f4e20 r14: ffffffff804bc1a0
(XEN) r15: 000000629838fcd8 cr0: 000000008005003b cr3: 0000000009137000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e010
(XEN) Xen stack trace from rsp=ffff830000222fe8:
(XEN) (file=extable.c, line=77) Pre-exception: ffff83000015773e ->
0000000000000000
(XEN) Assertion 'diff < STACK_SIZE' failed, line 38, file traps.c
(XEN) BUG at traps.c:38
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bca48 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bc820 ->
0000000000000000
(XEN) Assertion 'diff < STACK_SIZE' failed, line 38, file traps.c
(XEN) BUG at traps.c:38
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001bca48 ->
0000000000000000
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 2196608
(XEN) RIP: e010:[<ffff8300001bca48>] show_registers+0x264/0x752
(XEN) RFLAGS: 0000000000010086 CONTEXT: hypervisor
(XEN) rax: ffff8300001e70e4 rbx: ffff8300002230b8 rcx: 00000000000032dc
(XEN) rdx: 0000000000000000 rsi: 000000000000000a rdi: ffff8300001e70e4
(XEN) rbp: ffff830000218098 rsp: ffff830000217f08 r8: 00000000ffffffff
(XEN) r9: 00000000ffffffff r10: ffff83000022ed3f r11: ffff83000022e94f
(XEN) r12: ffffffff804bc220 r13: 000001000d3f4e20 r14: ffffffff804bc1a0
(XEN) r15: 000000629838fcd8 cr0: 000000008005003b cr3: 0000000009137000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e010
(XEN) Xen stack trace from rsp=ffff830000217f08:
(XEN) 0000000a00000000 ffff8300001e71a0 0000000000000000 ffff830000218108
(XEN) ffff830000217f58 ffff83000012cd48 0000000a00000000 ffff8300001e71a0
(XEN) ffff830000217fe8 ffff8300001e7214 ffff830000217f98 0000000000000082
(XEN) ffff8300001d0a1a 000000080000004d 0000000a00000009 ffff8300001e71a0
(XEN) 000000629838fcd8 ffffffff804bc1a0 000001000d3f4e20 ffffffff804bc220
(XEN) ffff830000218348 ffff8300002230b8 ffff83000022e956 ffff83000022e97d
(XEN) 00000000ffffffff 0000000000000010 0000000a00000009 0000000000000000
(XEN) 00000000000000c8 ffff830000218480 ffff830000218300
(XEN) Xen call trace:
(XEN) [<ffff8300001bca48>] show_registers+0x264/0x752
(XEN)
(XEN) ************************************
(XEN) CPU2196608 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN
INTERRUPT CONTEXT.
(XEN) System shutting down -- need manual reset.
(XEN) ************************************
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
next prev parent reply other threads:[~2006-07-25 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 16:02 BUG: x86-64 VT crash backtrace Rik van Riel
2006-07-25 16:55 ` Rik van Riel [this message]
2006-07-25 17:12 ` Keir Fraser
2006-07-25 16:57 ` Keir Fraser
2006-07-25 17:09 ` Rik van Riel
2006-07-25 17:15 ` Keir Fraser
2006-07-25 18:42 ` Rik van Riel
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=44C64D19.7020002@redhat.com \
--to=riel@redhat.com \
--cc=jun.nakajima@intel.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.