* [BUG] X86-64 dom0 oops if dom0_mem not specified
@ 2005-04-26 14:53 Jerone Young
0 siblings, 0 replies; 2+ messages in thread
From: Jerone Young @ 2005-04-26 14:53 UTC (permalink / raw)
To: xen-devel
>From my observations if you don't pass dom0_mem or you pass dom0_mem
with a value greater that 256000, Dom0 will oops on boot. Here is some
output from the oops:
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE'(XEN) PHYSICAL
MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000040000000->0000000080000000 (641881 pages
to be al)(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80100000->ffffffff80516085
(XEN) Init. ramdisk: ffffffff80517000->ffffffff80517000
(XEN) Phys-Mach map: ffffffff80517000->ffffffff80889d64
(XEN) Page tables: ffffffff8088a000->ffffffff80893000
(XEN) Start info: ffffffff80893000->ffffffff80894000
(XEN) Boot stack: ffffffff80894000->ffffffff80895000
(XEN) TOTAL: ffffffff80000000->ffffffff80c00000
(XEN) ENTRY ADDRESS: ffffffff80100000
(XEN) Scrubbing Free RAM: ....................................done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xe. Xen: 0000000000000000 - 00000000dcb59000 (usable)
(XEN) BUG at domain.c:136
(XEN) CPU: 0
(XEN) EIP: 0810:[<ffff830000107369>]
(XEN) EFLAGS: 0000000000010292
(XEN) rax: 0000000000000000 rbx: ffff830000fecb80 rcx:
00000000000003f8 r5(XEN) rsi: 000000000000000a rdi: ffff830000160474
rbp: 00000000dcb59000 r8(XEN) r8: 0000000000000036 r9:
0000000000001996 r10: 0000000000000001 r4(XEN) r12: ffffffff80a95b50
r13: 000000000000016a r14: 0000000000000001 r8(XEN) Stack trace from
RSP=ffff830000105ee8:
(XEN) [ffff830000107450] ffff830000fea080 00000000dcb59000
[ffff83000010745
(XEN) 000000000000016a ffffffff80a95b50 00000000dcb59000
ffffffff80c00000 0
(XEN) 0000000000000000 0000000000000000 0000000000000000
0000000000000000 f
(XEN) 0000000000010216 ffffffff80104040 000000000000082b
0000000000000000 0
(XEN) 0000000000000000 0000000000000000 ffff830000fea080
(XEN) Call Trace from RSP=ffff830000105ee8:
(XEN) [<ffff830000107450>] [<ffff830000107459>] [<ffff830000137596>]
****************************************
CPU0 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
Aieee! CPU0 is toast...
****************************************
--
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)
^ permalink raw reply [flat|nested] 2+ messages in thread
* RE: [BUG] X86-64 dom0 oops if dom0_mem not specified
@ 2005-04-27 15:21 Nakajima, Jun
0 siblings, 0 replies; 2+ messages in thread
From: Nakajima, Jun @ 2005-04-27 15:21 UTC (permalink / raw)
To: Jerone Young, xen-devel
Jerone Young wrote:
>> From my observations if you don't pass dom0_mem or you pass dom0_mem
> with a value greater that 256000, Dom0 will oops on boot. Here is some
> output from the oops:
I'm taking a look at this problem.
Jun
>
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
> 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE'(XEN) PHYSICAL
> MEMORY ARRANGEMENT:
> (XEN) Dom0 alloc.: 0000000040000000->0000000080000000 (641881 pages
> to be al)(XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN) Loaded kernel: ffffffff80100000->ffffffff80516085
> (XEN) Init. ramdisk: ffffffff80517000->ffffffff80517000
> (XEN) Phys-Mach map: ffffffff80517000->ffffffff80889d64
> (XEN) Page tables: ffffffff8088a000->ffffffff80893000
> (XEN) Start info: ffffffff80893000->ffffffff80894000
> (XEN) Boot stack: ffffffff80894000->ffffffff80895000
> (XEN) TOTAL: ffffffff80000000->ffffffff80c00000
> (XEN) ENTRY ADDRESS: ffffffff80100000
> (XEN) Scrubbing Free RAM: ....................................done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xe. Xen: 0000000000000000 - 00000000dcb59000 (usable)
> (XEN) BUG at domain.c:136
> (XEN) CPU: 0
> (XEN) EIP: 0810:[<ffff830000107369>]
> (XEN) EFLAGS: 0000000000010292
> (XEN) rax: 0000000000000000 rbx: ffff830000fecb80 rcx:
> 00000000000003f8 r5(XEN) rsi: 000000000000000a rdi:
> ffff830000160474 rbp: 00000000dcb59000 r8(XEN) r8:
> 0000000000000036 r9: 0000000000001996 r10: 0000000000000001
> r4(XEN) r12: ffffffff80a95b50 r13: 000000000000016a r14:
> 0000000000000001 r8(XEN) Stack trace from RSP=ffff830000105ee8:
> (XEN) [ffff830000107450] ffff830000fea080 00000000dcb59000
> [ffff83000010745
> (XEN) 000000000000016a ffffffff80a95b50 00000000dcb59000
> ffffffff80c00000 0
> (XEN) 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 f
> (XEN) 0000000000010216 ffffffff80104040 000000000000082b
> 0000000000000000 0
> (XEN) 0000000000000000 0000000000000000 ffff830000fea080
> (XEN) Call Trace from RSP=ffff830000105ee8:
> (XEN) [<ffff830000107450>] [<ffff830000107459>]
> [<ffff830000137596>]
>
> ****************************************
> CPU0 FATAL TRAP: vector = 6 (invalid operand)
> [error_code=0000]
> Aieee! CPU0 is toast...
> ****************************************
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-04-27 15:21 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-26 14:53 [BUG] X86-64 dom0 oops if dom0_mem not specified Jerone Young
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 15:21 Nakajima, Jun
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.