The log showed below:
PID hash table entries: 4096 (order: 12, 32768 bytes)
Console: colour VGA+ 80x25
Kernel panic - not syncing: Failed to setup Xen contiguous region
<1>Unable to handle kernel NULL pointer dereference (address 0000000000000000)
swapper[0]: Oops 11012296146944 [1]
Modules linked in:
Pid: 0, CPU 0, comm: swapper
psr : 00001210084a2010 ifs : 8000000000000389 ip : [<a0000001001300d1>] Not
tainted
ip is at kmem_cache_alloc+0x131/0x2e0
unat: 0000000000000000 pfs : 4000000000000793 rsc : 0000000000000007
rnat: 0000000000000000 bsps: 0000000000000000 pr : 0000000000005989
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f
csd : 0000000000000000 ssd : 0000000000000000
b0 : a00000010004a2c0 b6 : a00000010004b0a0 b7 : a000000100014d70
f6 : 1003e5b51e7d1b1a1644c f7 : 1003e9e3779b97f4a7c16
f8 : 1003e0a00000010003c32 f9 : 1003e000000000000007f
f10 : 1003e0000000000000379 f11 : 1003e6db6db6db6db6db7
r1 : a000000101146090 r2 : 0000000000000001 r3 : fffffffffff00001
r8 : fffffffffff04c18 r9 : 0000000000000000 r10 : 0000000000000001
r11 : 0000000000000000 r12 : a000000100d0f6a0 r13 : a000000100d08000
r14 : 0000000000000001 r15 : fffffffffff00001 r16 : 0000000000000000
r17 : 0000000012000000 r18 : a000000100d08018 r19 : a000000100d0f72c
r20 : a000000100d0f728 r21 : 0000000000000000 r22 : 0000000000000000
r23 : a000000100d08f24 r24 : a00000010003c300 r25 : a000000100000000
r26 : a000000100d93aa0 r27 : a000000100f47600 r28 : a000000100d8dff0
r29 : a000000100d8dfe0 r30 : 00000000000001eb r31 : 000000000003c340
I didn't set dom0_mem values in elilo.conf? what is defaut value? my elilo.conf
likes below:
image=vmlinuz-2.6-xen0
label=xen
vmm=xen.gz
initrd=initrd-3.0.img
read-only
append="sched=credit -- nomca console=tty0 console=ttyS0,57600,8n1
root=/dev/sda3 max_loop=32"
>-----Original Message-----
>From: Jarod Wilson [mailto:jwilson@xxxxxxxxxx]
>Sent: 2007年8月24日 13:35
>To: Zhang, Xing Z
>Cc: Alex Williamson; xen-ia64-devel; Masaki Kanno
>Subject: Re: [Xen-ia64-devel] [BUG]Dom0 panic if "dom0_mem"
>field is notexplicitly set in elilo.conf
>
>Zhang, Xing Z wrote:
>> I tried it again on two boxes. One has 2G memory, another
>one has 4G memory.
>> If I didnt' set "dom0_mem" in elilo.conf, both boxes meet
>panic in booting time.
>> I ever used "xm info" to look up availble memory, the 2G
>one has 2023M, the 4G
>> one has 4071M. Then I set "dom0_mem=2023M" for 2G one and
>"dom0_mem=4071M"
>> for 4G one. The panic meet again.
>
>Can you provide a console boot log somewhere? I'm not able to produce
>the problem
>on any of the boxes I've got access to, which now ranges from a 4G box
>to a 16G box
>to a 120G box... Also, what dom0_mem values let the boxes boot?
>
>
>>> -----Original Message-----
>>> From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>>> Sent: 2007年8月23日 20:15
>>> To: Zhang, Xing Z
>>> Cc: xen-ia64-devel
>>> Subject: Re: [Xen-ia64-devel] [BUG]Dom0 panic if "dom0_mem"
>>> field is notexplicitly set in elilo.conf
>>>
>>> On Thu, 2007-08-23 at 13:36 +0800, Zhang, Xing Z wrote:
>>>> Hi All:
>>>> I found in current changeset, if you don't explicitly set
>>>> "dom0_mem" field in elilo.conf then a kernel panic raises.
>Error info
>>>> showed below.
>>>> I am not sure which changeset leads this bug, but CSET15410 is
>>>> fine. Did anyone meet this?
>>> I haven't seen this failure. How much memory is in your system?
>
>--
>Jarod Wilson
>jwilson@xxxxxxxxxx
>
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home