* xen-unstable domU smp broken for vcpus > physical cpus
@ 2005-04-01 23:25 Ryan Harper
2005-04-01 23:40 ` Anthony Liguori
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Ryan Harper @ 2005-04-01 23:25 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
Hi,
Rik mentioned in #xen on irc.oftc.net that his smp domU was crashing.
Mine was working and we started to investigate. Turns out that using
xen-unstable from 2005-04-01 when domU is launched with vcpus > physical
cpus, domU, and in my case, Xen itself crash. Attached is the debug log
of Xen going down.
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
[-- Attachment #2: xen_20050401_domU_crashes_xen.oops --]
[-- Type: text/plain, Size: 2453 bytes --]
(XEN) Assertion '(x & PGT_count_mask) != 0' failed, line 1087, file mm.c
(XEN) BUG at mm.c:1087
(XEN) CPU: 1
(XEN) EIP: 0808:[<fc520bfb>]
(XEN) EFLAGS: 00010292 CONTEXT: hypervisor
(XEN) eax: fc562191 ebx: f0000000 ecx: 00000000 edx: 00000000
(XEN) esi: fc5553d0 edi: f0000000 ebp: efffffff esp: fcff9d24
(XEN) ds: 0810 es: 0810 fs: 0810 gs: 0810 ss: 0810 cs: 0808
(XEN) Stack trace from ESP=fcff9d24:
(XEN) fc54d1ba fc555eda 0000043f fc555eda 075e0000 00000004 00000000 fc000000
(XEN) c00245b4 c00245b8 00000000 fd4b0010 fcffac40 00000958 fcffac40 [fc529678]
(XEN) fd4b0010 e0000000 00000001 000006c0 fc56a6c0 0000001b fcff9db8 [fc51eebf]
(XEN) fd93faa8 fcffac40 80000002 80000003 80000002 fcffac40 fcffac40 fd4b7810
(XEN) 07556063 07a56000 00000004 07a56000 fc558248 c0025958 07a56000 [fc52925b]
(XEN) c0025958 00000000 07a56000 00000004 00000000 00000004 0000004e [fc536c35]
(XEN) c0025958 07a56000 00000004 00000004 00000040 [fc50f14a] [fc520c1e] 00000808
(XEN) 0651cd76 00000000 00000000 00000004 00000000 006dc0a0 00000000 006dc0a0
(XEN) 00000000 a9470320 00000034 0000e76d fcfe7089 fcff3bac fcfe7040 00000040
(XEN) [fc50f14a] 00000292 fcfb9040 00000002 00000040 00000001 fcffb640 aec00b55
(XEN) 00000092 fcffb640 fc561790 fffffffc 00000006 00000092 00003700 00000089
(XEN) c10004a0 07a56000 00000063 c0025958 c1000000 00000000 07a56000 000e0003
(XEN) c0114a2b 00000061 00010246 c7a4fe3c 00000069 0000007b 0000007b 00000000
(XEN) 00000000 ff913000 fcffac40 20000000 00000001 00000004 07a56000 07556063
(XEN) c0025958 075e0000 c7a4fe1c 0000000c 00000000 00000004 07a56000 07a56000
(XEN) fcff9e9c 00000034 fcffac40 00000000 fd4b0d00 00000000 fcffac40 c0025958
(XEN) fcff9fb8 fcfe6040 fc558248 [fc5255eb] fcff9fb8 c0025958 fc558248 00000004
(XEN) fc561204 fc561204 c7a4fb58 fcfe6040 37fc7061 fcffac40 80000002 fcfe6040
(XEN) fcffac40 00037fc7 19ee6b00 fcffac40 c0025958 fcfe6040 fcff9fb8 [fc530262]
(XEN) c0025958 00000006 c131ef20 c0114d38 00000000 075e0bfc 00000000 fcfe6040
(XEN) Call Trace from ESP=fcff9d24:
(XEN) [<fc529678>] [<fc51eebf>] [<fc52925b>] [<fc536c35>] [<fc50f14a>] [<fc520c1e>]
(XEN) [<fc50f14a>] [<fc5255eb>] [<fc530262>] [<fc53981e>]
****************************************
CPU1 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
Aieee! CPU1 is toast...
****************************************
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: xen-unstable domU smp broken for vcpus > physical cpus
2005-04-01 23:25 xen-unstable domU smp broken for vcpus > physical cpus Ryan Harper
@ 2005-04-01 23:40 ` Anthony Liguori
2005-04-02 1:24 ` Rik van Riel
2005-04-02 7:34 ` Keir Fraser
2 siblings, 0 replies; 9+ messages in thread
From: Anthony Liguori @ 2005-04-01 23:40 UTC (permalink / raw)
To: Ryan Harper; +Cc: xen-devel
[-- Attachment #1: Type: text/plain, Size: 3432 bytes --]
I can reproduce reliably. My setup is vcpus > physical in domU. SMP
is disabled in dom0. Only my linux kernel crashes (in domU). Attached
is the oops.
Ryan Harper wrote:
>Hi,
>
>Rik mentioned in #xen on irc.oftc.net that his smp domU was crashing.
>Mine was working and we started to investigate. Turns out that using
>xen-unstable from 2005-04-01 when domU is launched with vcpus > physical
>cpus, domU, and in my case, Xen itself crash. Attached is the debug log
>of Xen going down.
>
>Ryan Harper
>Software Engineer; Linux Technology Center
>IBM Corp., Austin, Tx
>(512) 838-9253 T/L: 678-9253
>ryanh@us.ibm.com
>
>
>------------------------------------------------------------------------
>
>(XEN) Assertion '(x & PGT_count_mask) != 0' failed, line 1087, file mm.c
>(XEN) BUG at mm.c:1087
>(XEN) CPU: 1
>(XEN) EIP: 0808:[<fc520bfb>]
>(XEN) EFLAGS: 00010292 CONTEXT: hypervisor
>(XEN) eax: fc562191 ebx: f0000000 ecx: 00000000 edx: 00000000
>(XEN) esi: fc5553d0 edi: f0000000 ebp: efffffff esp: fcff9d24
>(XEN) ds: 0810 es: 0810 fs: 0810 gs: 0810 ss: 0810 cs: 0808
>(XEN) Stack trace from ESP=fcff9d24:
>(XEN) fc54d1ba fc555eda 0000043f fc555eda 075e0000 00000004 00000000 fc000000
>(XEN) c00245b4 c00245b8 00000000 fd4b0010 fcffac40 00000958 fcffac40 [fc529678]
>(XEN) fd4b0010 e0000000 00000001 000006c0 fc56a6c0 0000001b fcff9db8 [fc51eebf]
>(XEN) fd93faa8 fcffac40 80000002 80000003 80000002 fcffac40 fcffac40 fd4b7810
>(XEN) 07556063 07a56000 00000004 07a56000 fc558248 c0025958 07a56000 [fc52925b]
>(XEN) c0025958 00000000 07a56000 00000004 00000000 00000004 0000004e [fc536c35]
>(XEN) c0025958 07a56000 00000004 00000004 00000040 [fc50f14a] [fc520c1e] 00000808
>(XEN) 0651cd76 00000000 00000000 00000004 00000000 006dc0a0 00000000 006dc0a0
>(XEN) 00000000 a9470320 00000034 0000e76d fcfe7089 fcff3bac fcfe7040 00000040
>(XEN) [fc50f14a] 00000292 fcfb9040 00000002 00000040 00000001 fcffb640 aec00b55
>(XEN) 00000092 fcffb640 fc561790 fffffffc 00000006 00000092 00003700 00000089
>(XEN) c10004a0 07a56000 00000063 c0025958 c1000000 00000000 07a56000 000e0003
>(XEN) c0114a2b 00000061 00010246 c7a4fe3c 00000069 0000007b 0000007b 00000000
>(XEN) 00000000 ff913000 fcffac40 20000000 00000001 00000004 07a56000 07556063
>(XEN) c0025958 075e0000 c7a4fe1c 0000000c 00000000 00000004 07a56000 07a56000
>(XEN) fcff9e9c 00000034 fcffac40 00000000 fd4b0d00 00000000 fcffac40 c0025958
>(XEN) fcff9fb8 fcfe6040 fc558248 [fc5255eb] fcff9fb8 c0025958 fc558248 00000004
>(XEN) fc561204 fc561204 c7a4fb58 fcfe6040 37fc7061 fcffac40 80000002 fcfe6040
>(XEN) fcffac40 00037fc7 19ee6b00 fcffac40 c0025958 fcfe6040 fcff9fb8 [fc530262]
>(XEN) c0025958 00000006 c131ef20 c0114d38 00000000 075e0bfc 00000000 fcfe6040
>(XEN) Call Trace from ESP=fcff9d24:
>(XEN) [<fc529678>] [<fc51eebf>] [<fc52925b>] [<fc536c35>] [<fc50f14a>] [<fc520c1e>]
>(XEN) [<fc50f14a>] [<fc5255eb>] [<fc530262>] [<fc53981e>]
>
>****************************************
>CPU1 FATAL TRAP: vector = 6 (invalid operand)
>[error_code=0000]
>Aieee! CPU1 is toast...
>****************************************
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
[-- Attachment #2: xen.log --]
[-- Type: text/x-log, Size: 1716 bytes --]
/ # (sleep 3; rm test) &
/ # Failed update VA mapping: 0809d730, 16d00067, 00000000
------------[ cut here ]------------
kernel BUG at <bad filename>:13289!
invalid operand: 0000 [#1]
PREEMPT SMP
Modules linked in:
CPU: 1
EIP: 0061:[<c0147a66>] Not tainted VLI
EFLAGS: 00010296 (2.6.11-xenU)
EIP is at do_wp_page+0x2a6/0x420
eax: 0000003a ebx: 0809d730 ecx: fbffc008 edx: 00000000
esi: 16d00067 edi: 0809d730 ebp: c1002020 esp: c0313e94
ds: 0069 es: 0069 ss: 0069
Process rm (pid: 88, threadinfo=c0312000 task=c0750060)
Stack: c02a2e84 0809d730 16d00067 00000000 c7c4eb00 c10f8ae0 c7c46080 c7c4eac0
0809d730 c7c4eb00 c0148c65 c7c4eac0 c032b0cc 0809d730 c7e50274 c7c46080
02856025 00000000 c7c4eac0 c7c4eaec 00000007 c032b0cc c01138dc c7c4eac0
Call Trace:
[<c0148c65>] handle_mm_fault+0x1b5/0x1d0
[<c01138dc>] do_page_fault+0x19c/0x6a7
[<c0313fc4>] makecrc+0x54/0x90
[<c0313fc4>] makecrc+0x54/0x90
[<c0162088>] copy_strings+0x188/0x200
[<c01802a0>] load_elf_binary+0x0/0xc40
[<c0312000>] initrd_load+0x0/0x90
[<c016344f>] search_binary_handler+0x25f/0x2b0
[<c0313fc4>] makecrc+0x54/0x90
[<c0163648>] do_execve+0x1a8/0x220
[<c0313fc4>] makecrc+0x54/0x90
[<c0312000>] initrd_load+0x0/0x90
[<c0318000>] smp_store_cpu_info+0xd0/0xe0
[<c0312000>] initrd_load+0x0/0x90
[<c010839d>] sys_execve+0x5d/0xa0
[<c0318000>] smp_store_cpu_info+0xd0/0xe0
[<c0312000>] initrd_load+0x0/0x90
[<c0109dfa>] page_fault+0x4e/0x54
Code: 89 d0 e8 2e a9 ff ff eb ba 0f 0b eb a6 89 74 24 08 31 c0 89 44 24 0c 8b 44 24 34 c7 04 24 84 2e 2a c0 89 44 24 04 e8 aa 3c fd ff <0f> 0b e9 33 ff ff ff 89 74 24 04 8b 54 24 38 89 14 24 e8 43 c7
<6>note: rm[88] exited with preempt_count 1
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: xen-unstable domU smp broken for vcpus > physical cpus
2005-04-01 23:25 xen-unstable domU smp broken for vcpus > physical cpus Ryan Harper
2005-04-01 23:40 ` Anthony Liguori
@ 2005-04-02 1:24 ` Rik van Riel
2005-04-02 7:34 ` Keir Fraser
2 siblings, 0 replies; 9+ messages in thread
From: Rik van Riel @ 2005-04-02 1:24 UTC (permalink / raw)
To: Ryan Harper; +Cc: xen-devel
On Fri, 1 Apr 2005, Ryan Harper wrote:
> Rik mentioned in #xen on irc.oftc.net that his smp domU was crashing.
> Mine was working and we started to investigate. Turns out that using
> xen-unstable from 2005-04-01 when domU is launched with vcpus > physical
> cpus, domU, and in my case, Xen itself crash. Attached is the debug log
> of Xen going down.
Interesting, I haven't made Xen itself crash. Here are the
config options that may be relevant:
CONFIG_XEN=y
CONFIG_ARCH_XEN=y
CONFIG_NO_IDLE_HZ=y
#
# XEN
#
# CONFIG_XEN_PRIVILEGED_GUEST is not set
# CONFIG_XEN_PHYSDEV_ACCESS is not set
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_XEN_NETDEV_FRONTEND_PIPELINED_TRANSMITTER is not set
# CONFIG_XEN_BLKDEV_TAP is not set
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_X86=y
# CONFIG_X86_64 is not set
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y
--
"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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: xen-unstable domU smp broken for vcpus > physical cpus
2005-04-01 23:25 xen-unstable domU smp broken for vcpus > physical cpus Ryan Harper
2005-04-01 23:40 ` Anthony Liguori
2005-04-02 1:24 ` Rik van Riel
@ 2005-04-02 7:34 ` Keir Fraser
2005-04-02 8:31 ` Ryan Harper
2 siblings, 1 reply; 9+ messages in thread
From: Keir Fraser @ 2005-04-02 7:34 UTC (permalink / raw)
To: Ryan Harper; +Cc: xen-devel
On 2 Apr 2005, at 00:25, Ryan Harper wrote:
> Rik mentioned in #xen on irc.oftc.net that his smp domU was crashing.
> Mine was working and we started to investigate. Turns out that using
> xen-unstable from 2005-04-01 when domU is launched with vcpus >
> physical
> cpus, domU, and in my case, Xen itself crash. Attached is the debug
> log
> of Xen going down.
A link to the xen-syms file would make the backtrace more useful. Also
great would be to know in which changeset the bug first appeared: was
it actually 1st April, or is that just the only one you've tested with
vcpus > pcpus and so it could have been there for weeks or months?
-- Keir
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: xen-unstable domU smp broken for vcpus > physical cpus
2005-04-02 7:34 ` Keir Fraser
@ 2005-04-02 8:31 ` Ryan Harper
2005-04-02 16:34 ` Ryan Harper
0 siblings, 1 reply; 9+ messages in thread
From: Ryan Harper @ 2005-04-02 8:31 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel
* Keir Fraser <Keir.Fraser@cl.cam.ac.uk> [2005-04-02 01:36]:
>
> On 2 Apr 2005, at 00:25, Ryan Harper wrote:
>
> >Rik mentioned in #xen on irc.oftc.net that his smp domU was crashing.
> >Mine was working and we started to investigate. Turns out that using
> >xen-unstable from 2005-04-01 when domU is launched with vcpus >
> >physical
> >cpus, domU, and in my case, Xen itself crash. Attached is the debug
> >log
> >of Xen going down.
>
> A link to the xen-syms file would make the backtrace more useful. Also
Hrm, I always do the install.sh, shouldnt that set up the xen-syms file
correctly? What do I need to check to make sure the xen-syms file is
setup up for a more useful backtrace?
> great would be to know in which changeset the bug first appeared: was
> it actually 1st April, or is that just the only one you've tested with
> vcpus > pcpus and so it could have been there for weeks or months?
I'm fairly certain that I've had vcpus > pcpus in domU working fine as
recent as 2005-03-31, but I'll backtrack and verify.
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: xen-unstable domU smp broken for vcpus > physical cpus
2005-04-02 8:31 ` Ryan Harper
@ 2005-04-02 16:34 ` Ryan Harper
2005-04-02 20:37 ` Keir Fraser
2005-04-03 13:24 ` Keir Fraser
0 siblings, 2 replies; 9+ messages in thread
From: Ryan Harper @ 2005-04-02 16:34 UTC (permalink / raw)
To: Ryan Harper; +Cc: xen-devel
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
* Ryan Harper <ryanh@us.ibm.com> [2005-04-02 02:34]:
> * Keir Fraser <Keir.Fraser@cl.cam.ac.uk> [2005-04-02 01:36]:
> >
> > On 2 Apr 2005, at 00:25, Ryan Harper wrote:
> >
> > >Rik mentioned in #xen on irc.oftc.net that his smp domU was crashing.
> > >Mine was working and we started to investigate. Turns out that using
> > >xen-unstable from 2005-04-01 when domU is launched with vcpus >
> > >physical
> > >cpus, domU, and in my case, Xen itself crash. Attached is the debug
> > >log
> > >of Xen going down.
> >
>
> > great would be to know in which changeset the bug first appeared: was
> > it actually 1st April, or is that just the only one you've tested with
> > vcpus > pcpus and so it could have been there for weeks or months?
>
> I'm fairly certain that I've had vcpus > pcpus in domU working fine as
> recent as 2005-03-31, but I'll backtrack and verify.
I just built the 2005-03-31 snapshot, dom0 is SMP, two vcpus, and booted
domU with 4 vcpus with no problems. Building 2005-04-01 in a simliar
fashion now yields an oops in domU and one error [1]output from Xen.
I then went to destroy the domU that I created and Xen went down. And
appearently, I don't have xen-sysms set up right as nont of the
addresses are translated into function names.
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
1. (XEN)
(file=/home/rharper/work/openhype/xen/unstable/20050401/b/xen/include/asm/mm.h,
line=160) Error pfn 000073ae0
[-- Attachment #2: xen_20050401_domU_oops.txt --]
[-- Type: text/plain, Size: 3058 bytes --]
Unable to handle kernel paging request at virtual address c0025ff8
printing eip:
c0114b9f
*pde = ma 20838067 pa 00374067
*pte = ma 37fc7061 pa 00025061
[<c0114c07>] change_page_attr+0x47/0x60
[<c0114d38>] kernel_map_pages+0x28/0x40
[<c013c9fa>] prep_new_page+0x7a/0x90
[<c013cecf>] buffered_rmqueue+0x15f/0x270
[<c013d48a>] __alloc_pages+0x3fa/0x420
[<c0170b63>] dput+0x33/0x1d0
[<c0148f9c>] do_wp_page+0xac/0x420
[<c0314dcc>] inflate_dynamic+0x2dc/0x610
[<c0313b7c>] rd_load_image+0x23c/0x330
[<c0314d8c>] inflate_dynamic+0x29c/0x610
[<c0314dcc>] inflate_dynamic+0x2dc/0x610
[<c014a395>] handle_mm_fault+0x1b5/0x1d0
[<c0314d8c>] inflate_dynamic+0x29c/0x610
[<c0313b7c>] rd_load_image+0x23c/0x330
[<c0314d8c>] inflate_dynamic+0x29c/0x610
[<c0314db8>] inflate_dynamic+0x2c8/0x610
[<c011395c>] do_page_fault+0x19c/0x6a7
[<c0314d8c>] inflate_dynamic+0x29c/0x610
[<c0114bed>] change_page_attr+0x2d/0x60
[<c0114d38>] kernel_map_pages+0x28/0x40
[<c0141ca8>] cache_free_debugcheck+0x188/0x2c0
[<c0142901>] kmem_cache_free+0x51/0xd0
[<c015878c>] sys_open+0x6c/0x90
[<c015878c>] sys_open+0x6c/0x90
[<c0109dfa>] page_fault+0x4e/0x54
Oops: 0003 [#1]
PREEMPT SMP DEBUG_PAGEALLOC
Modules linked in:
CPU: 0
EIP: 0061:[<c0114b9f>] Not tainted VLI
EFLAGS: 00010206 (2.6.11-xenU-smp)
EIP is at __change_page_attr+0x20f/0x230
eax: 073ae063 ebx: c10004a0 ecx: 00000063 edx: 00007bfe
esi: c0025ff8 edi: c1000000 ebp: 00000063 esp: c0051dbc
ds: 0069 es: 0069 ss: 0069
Process init (pid: 1, threadinfo=c0050000 task=c137baf0)
Stack: c7bfe000 00000002 c7b11244 c7bfe000 c10f7fc0 00000000 00000000 00000000
c0114c07 c10f7fc0 00000063 c10f7fc0 00000000 00000001 c02d74a0 c0114d38
c10f7fc0 00000001 00000063 c013c9fa c10f7fc0 00000001 00000001 00000030
Call Trace:
[<c0114c07>] change_page_attr+0x47/0x60
[<c0114d38>] kernel_map_pages+0x28/0x40
[<c013c9fa>] prep_new_page+0x7a/0x90
[<c013cecf>] buffered_rmqueue+0x15f/0x270
[<c013d48a>] __alloc_pages+0x3fa/0x420
[<c0170b63>] dput+0x33/0x1d0
[<c0148f9c>] do_wp_page+0xac/0x420
[<c0314dcc>] inflate_dynamic+0x2dc/0x610
[<c0313b7c>] rd_load_image+0x23c/0x330
[<c0314d8c>] inflate_dynamic+0x29c/0x610
[<c0314dcc>] inflate_dynamic+0x2dc/0x610
[<c014a395>] handle_mm_fault+0x1b5/0x1d0
[<c0314d8c>] inflate_dynamic+0x29c/0x610
[<c0313b7c>] rd_load_image+0x23c/0x330
[<c0314d8c>] inflate_dynamic+0x29c/0x610
[<c0314db8>] inflate_dynamic+0x2c8/0x610
[<c011395c>] do_page_fault+0x19c/0x6a7
[<c0314d8c>] inflate_dynamic+0x29c/0x610
[<c0114bed>] change_page_attr+0x2d/0x60
[<c0114d38>] kernel_map_pages+0x28/0x40
[<c0141ca8>] cache_free_debugcheck+0x188/0x2c0
[<c0142901>] kmem_cache_free+0x51/0xd0
[<c015878c>] sys_open+0x6c/0x90
[<c015878c>] sys_open+0x6c/0x90
[<c0109dfa>] page_fault+0x4e/0x54
Code: 24 24 29 f9 c1 f9 05 c1 e1 0c 09 d1 f6 c1 01 89 c8 74 18 a1 00 88 33 c0 89 ca c1 ea 0c 81 e1 ff 0f 00 00 8b 04 90 c1 e0 0c 09 c8 <89> 06 f0 ff 4b 04 e9 85 fe ff ff 8d b6 00 00 00 00 0f 0b e9 78
<0>Kernel panic - not syncing: Attempted to kill init!
[-- Attachment #3: xen_20050401_xen_oops.txt --]
[-- Type: text/plain, Size: 2137 bytes --]
(XEN) Assertion '(pg[i].u.inuse.type_info & PGT_count_mask) == 0' failed, line 563, file page_alloc.c
(XEN) BUG at page_alloc.c:563
(XEN) CPU: 0
(XEN) EIP: 0808:[<fc50cdea>]
(XEN) EFLAGS: 00010292 CONTEXT: hypervisor
(XEN) eax: fc562198 ebx: fd4b0238 ecx: 00000000 edx: 00000000
(XEN) esi: 00000001 edi: fcffac40 ebp: fd4b0238 esp: fc503e08
(XEN) ds: 0810 es: 0810 fs: 0810 gs: 0810 ss: 0810 cs: 0808
(XEN) Stack trace from ESP=fc503e08:
(XEN) fc54d1ba fc54d478 00000233 fc54d478 ffa5f000 00000000 00000000 00000001
(XEN) fcffac40 fd4b0220 fd4b0238 [fc51a4ed] fd4b0238 00000000 fcfe50dc fd71df58
(XEN) 00000000 fcfbc040 fd71df58 [fc526f2e] fd71df58 fcff3880 fd4b0238 fcffac5c
(XEN) fcffac54 fcffac40 00000001 [fc51966d] fcffac40 fcffac54 00000001 [fc510246]
(XEN) 00000000 fcffac40 fcffac40 [fc5062f7] fcffac40 fcff2040 00000000 [fc505134]
(XEN) fcffac40 bfffd410 00000050 00000069 00000292 fcff2040 00000001 [fc52ed3b]
(XEN) 26f25000 fcff3880 40000000 00000001 00000000 00000000 00000001 [fc52233d]
(XEN) 00000001 406ad000 0000000c 00000000 00000004 140ba000 140ba000 fc503e9c
(XEN) fcfbe040 00000202 00000001 00000001 26818065 fed01ab4 fd79c240 [fc52825f]
(XEN) fd79c240 e0000000 [fc5255eb] fc503fb8 c00562e8 fc558248 00000004 ffffffda
(XEN) 00000009 aaaa1002 40770001 080766fa 4077f8c8 08274ce0 00000000 401d202c
(XEN) 4077979c 406f73c4 bfffd468 080ca8bf 401d202c 4077979c 406f73c5 406fa764
(XEN) bfffd458 401eeba0 bfffd484 406faa50 fc5611c0 00000000 00000000 fcff2040
(XEN) 40771700 401d202c 00185000 [fc5395d3] bfffd410 bfffd3f8 080fde6a 40771700
(XEN) 401d202c 00185000 00000007 000e0007 c028ea21 00000061 00000246 d910dd44
(XEN) 00000069 0000007b 0000007b 00000000 00000000 fcff2040
(XEN) Call Trace from ESP=fc503e08:
(XEN) [<fc51a4ed>] [<fc526f2e>] [<fc51966d>] [<fc510246>] [<fc5062f7>] [<fc505134>]
(XEN) [<fc52ed3b>] [<fc52233d>] [<fc52825f>] [<fc5255eb>] [<fc5395d3>]
****************************************
CPU0 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
Aieee! CPU0 is toast...
****************************************
[-- Attachment #4: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: xen-unstable domU smp broken for vcpus > physical cpus
2005-04-02 16:34 ` Ryan Harper
@ 2005-04-02 20:37 ` Keir Fraser
2005-04-03 13:24 ` Keir Fraser
1 sibling, 0 replies; 9+ messages in thread
From: Keir Fraser @ 2005-04-02 20:37 UTC (permalink / raw)
To: Ryan Harper; +Cc: xen-devel
On 2 Apr 2005, at 17:34, Ryan Harper wrote:
> I just built the 2005-03-31 snapshot, dom0 is SMP, two vcpus, and
> booted
> domU with 4 vcpus with no problems. Building 2005-04-01 in a simliar
> fashion now yields an oops in domU and one error [1]output from Xen.
> I then went to destroy the domU that I created and Xen went down. And
> appearently, I don't have xen-sysms set up right as nont of the
> addresses are translated into function names.
What are the top-of-tree changeset dates on these two snapshots? It'd
be good to know what range of changesets to drill down on. The relevant
changeset info is one of the first things that Xen prints out after the
vanity banner during boot.
-- Keir
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: xen-unstable domU smp broken for vcpus > physical cpus
2005-04-02 16:34 ` Ryan Harper
2005-04-02 20:37 ` Keir Fraser
@ 2005-04-03 13:24 ` Keir Fraser
2005-04-03 16:27 ` Rik van Riel
1 sibling, 1 reply; 9+ messages in thread
From: Keir Fraser @ 2005-04-03 13:24 UTC (permalink / raw)
To: Ryan Harper; +Cc: xen-devel
>> I'm fairly certain that I've had vcpus > pcpus in domU working fine as
>> recent as 2005-03-31, but I'll backtrack and verify.
>
> I just built the 2005-03-31 snapshot, dom0 is SMP, two vcpus, and
> booted
> domU with 4 vcpus with no problems. Building 2005-04-01 in a simliar
> fashion now yields an oops in domU and one error [1]output from Xen.
> I then went to destroy the domU that I created and Xen went down. And
> appearently, I don't have xen-sysms set up right as nont of the
> addresses are translated into function names.
The bug was actually in a changeset from late on 03-29, so it should
have caused crashes as far back as the 2005-03-30 snapshot (the one
taken on the morning on 03-30).
It's now fixed in the unstable repository - context switching between
VCPUs of the same domain incorrectly cleared that physical CPU from the
domain's bitmap.
-- Keir
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: xen-unstable domU smp broken for vcpus > physical cpus
2005-04-03 13:24 ` Keir Fraser
@ 2005-04-03 16:27 ` Rik van Riel
0 siblings, 0 replies; 9+ messages in thread
From: Rik van Riel @ 2005-04-03 16:27 UTC (permalink / raw)
To: Keir Fraser; +Cc: Ryan Harper, xen-devel
On Sun, 3 Apr 2005, Keir Fraser wrote:
> It's now fixed in the unstable repository - context switching between
> VCPUs of the same domain incorrectly cleared that physical CPU from the
> domain's bitmap.
Confirmed, booting xenU domains with vcpus=3 works again,
on my single P4 with HT. This fix will be in FC4 test 2.
--
"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
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2005-04-03 16:27 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-01 23:25 xen-unstable domU smp broken for vcpus > physical cpus Ryan Harper
2005-04-01 23:40 ` Anthony Liguori
2005-04-02 1:24 ` Rik van Riel
2005-04-02 7:34 ` Keir Fraser
2005-04-02 8:31 ` Ryan Harper
2005-04-02 16:34 ` Ryan Harper
2005-04-02 20:37 ` Keir Fraser
2005-04-03 13:24 ` Keir Fraser
2005-04-03 16:27 ` Rik van Riel
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.