| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
Re: [Xen-ia64-devel] [BUG]Dom0 panic if "dom0_mem" field is notexplicitl
Hi Wing,
No, I don't meet it.
[root@tiger201 ~]# xm info
host : tiger201.soft.fujitsu.com
release : 2.6.18-xen
version : #1 SMP Fri Aug 17 19:38:19 JST 2007
machine : ia64
nr_cpus : 16
nr_nodes : 1
sockets_per_node : 4
cores_per_socket : 2
threads_per_core : 2
cpu_mhz : 797
hw_caps :
00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:
total_memory : 8166
free_memory : 4020
node_to_cpu : node0:0-15
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-ia64 xen-3.0-ia64be hvm-3.0-ia64
xen_scheduler : credit
xen_pagesize : 16384
platform_params : virt_start=0xf000000000000000
xen_changeset : Thu Aug 16 13:46:50 2007 -0600 15760:049d4baa9965
cc_compiler : gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)
cc_compile_by : root
cc_compile_domain : soft.fujitsu.com
cc_compile_date : Mon Aug 20 15:45:26 JST 2007
xend_config_format : 4
[root@tiger201 ~]# cat /boot/efi/efi/redhat/elilo.conf
prompt
timeout=20
#default=linux
#default=kanno
default=kanno-test
relocatable
image=vmlinuz-2.6.18-8.el5
label=linux
initrd=initrd-2.6.18-8.el5.img
read-only
append="rhgb quiet root=LABEL=/"
image=../xen/vmlinuz-2.6.18-xen-kanno
label=kanno
vmm=../xen/xen.gz-kanno
initrd=../xen/initrd-2.6.18-xen.img-kanno
read-only
append="loglvl=all guest_loglvl=all -- 3 console=tty0 rhgb quiet
root=LABEL=/"
image=../xen/vmlinuz-2.6.18-xen-kanno
label=kanno-test
vmm=../xen/xen.gz-kanno-test
initrd=../xen/initrd-2.6.18-xen.img-kanno
read-only
append="loglvl=all guest_loglvl=all -- 3 console=tty0 rhgb quiet
root=LABEL=/"
Best regards,
Kan
Thu, 23 Aug 2007 13:36:01 +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?
>
>
>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
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
| |
|
Home