Hi Wilson:
This is full log. Hope it helpful
__ __ _____ ___ _ _ _
\ \/ /___ _ __ |___ / / _ \ _ _ _ __ ___| |_ __ _| |__ | | ___ 7015B3BC
\ // _ \ '_ \ |_ \| | | |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
/ \ __/ | | | ___) | |_| |__| |_| | | | \__ \ || (_| | |_) | | __/2438D367
/_/\_\___|_| |_| |____(_)___/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
76FE6615
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer LaboratoryScsi(Pun0,Lun0)/HD(Part4,SigA712BFFC
-9D57-4C35-A0AA-CA24240AEFBF)
Xen version 3.0-unstable (build@) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)
) Fri Aug 17 06:01:56 CST 2007
Latest ChangeSet: Thu Aug 16 13:46:50 2007 -0600 15760:049d4baa9965
(XEN) Xen command line: BOOT_IMAGE=scsi0:\EFI\redhat\xen.gz sched=credit
(XEN) xen image pstart: 0x4000000, xenheap pend: 0x8000000
(XEN) Xen patching physical address access by offset: 0x0
(XEN) find_memory: efi_memmap_walk returns max_page=1ffad
(XEN) Before xen_heap_start: f0000000041c5eb0
(XEN) After xen_heap_start: f0000000041cc000
(XEN) Init boot pages: 0x10000a8 -> 0x4000000.
(XEN) Init boot pages: 0x8000000 -> 0x7aed4000.
(XEN) Init boot pages: 0x7be522f0 -> 0x7c480010.
(XEN) Init boot pages: 0x7c480070 -> 0x7c483f91.
(XEN) Init boot pages: 0x7c483fc5 -> 0x7c487000.
(XEN) Init boot pages: 0x7c5c584d -> 0x7c5cc010.
(XEN) Init boot pages: 0x7c5cc8b0 -> 0x7d5b4000.
(XEN) Init boot pages: 0x7d600000 -> 0x7f708000.
(XEN) Init boot pages: 0x7fe58000 -> 0x7feb4000.
(XEN) System RAM: 2023MB (2071648kB)
(XEN) size of virtual frame_table: 5120kB
(XEN) virtual machine to physical table: f6fffffffff00298 size: 1056kB
(XEN) max_page: 0x1ffad
(XEN) allocating frame table/mpt table at mfn 0.
(XEN) Xen heap: 62MB (63696kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) avail:0x3170074000000000, status:0x74000000000,control:0x3170000000000000,
vm?0x10000000000
(XEN) WARNING: no opcode provided from hardware(0)!!!
(XEN) vm buffer size: 1048576, order: 6
(XEN) vm_buffer: 0xf000000007e00000
(XEN) register_intr: changing vector 39 from IO-SAPIC-edge to IO-SAPIC-level
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Time init:
(XEN) .... System Time: 3087414ns
(XEN) .... scale: 281BCCD14
(XEN) num_online_cpus=1, max_cpus=64
(XEN) Brought up 4 CPUs
(XEN) xenoprof: using perfmon.
(XEN) perfmon: version 2.0 IRQ 238
(XEN) perfmon: Montecito PMU detected, 27 PMCs, 35 PMDs, 12 counters (47 bits)
(XEN) Maximum number of domains: 63; 18 RID bits per domain
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Maximum permitted dom0 size: 1934MB
(XEN) Reducing dom0 memory allocation from 4194304K to 1980848K to fit available
memory
(XEN) Dom0 kernel: 64-bit, lsb, paddr 0x4000000 -> 0x53a9090
(XEN) METAPHYSICAL MEMORY ARRANGEMENT:
(XEN) Kernel image: 4000000->53a9090
(XEN) Entry address: 400ff20
(XEN) Init. ramdisk: 53b0000 len 13e84d
(XEN) Start info.: 53ac000->53b0000
(XEN) Dom0 max_vcpus=4
(XEN) Dom0: 0xf000000007cd4080
(XEN) enable lsapic entry: 0xf00000007ff7225c
(XEN) enable lsapic entry: 0xf00000007ff72268
(XEN) enable lsapic entry: 0xf00000007ff7228c
(XEN) enable lsapic entry: 0xf00000007ff72298
(XEN) ACPI_INTERRUPT_CPEI disabled for Domain0
(XEN) Domain0 EFI passthrough: MPS=0x7ff71000 ACPI 2.0=0x7ff72000 ACPI=0x7ff7300
0 SMBIOS=0xf0000
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen
).
(XEN) Freed 128kB init memory.
(XEN) vcpu_set_itc: Setting ar.itc is currently disabled (this message is only d
isplayed once)
(XEN) WARN: GSI 3 in use by Xen.
Linux version 2.6.18-xen (build@hp-build) (gcc version 3.4.6 20060404 (Red Hat 3
.4.6-3)) #1 SMP Fri Aug 17 06:15:23 CST 2007
EFI v1.00 by Xen/ia64: SALsystab=0x2178 MPS=0x7ff71000 ACPI 2.0=0x7ff72000 ACPI=
0x7ff73000 SMBIOS=0xf0000
booting generic kernel on platform dig
Initial ramdisk at: 0xe0000000053b0000 (1304653 bytes)
SAL 0.1: Xen/ia64 Xen/ia64 version 0.0
SAL: AP wakeup using external interrupt vector 0xf3
No logical to physical processor mapping available
ACPI: Local APIC address c0000000fee00000
iosapic_register_platform_intr: invalid int type 0xff
4 CPUs available, 16 CPUs total
Running on Xen! start_info_pfn=0x14eb nr_pages=123803 flags=0x3
Virtual mem_map starts at 0xa0007fffff970000
SMP: Allowing 16 CPUs, 12 hotplug CPUs
Built 1 zonelists. Total pages: 120515
Kernel command line: nomca console=tty0 console=ttyS0,57600,8n1 root=/dev/sda3 m
ax_loop=32 ro
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
>-----Original Message-----
>From: Jarod Wilson [mailto:jwilson@xxxxxxxxxx]
>Sent: 2007年8月25日 4:58
>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
>
>Zhang, Xing Z wrote:
>> The log showed below:
>
>I was actually interested in the entire boot log, if there's somewhere
>you could post it (probably a bit large for the list, so maybe pastebin
>it). I'm curious to see what amount is actually trying to be reserved
>and what the max you can actually boot with are. There should be output
>further up in the console boot log that says something along the lines
>of "Maximum permitted dom0 size: X MB". If you can boot with
>dom0_mem=YM, where Y is (X - a few megabytes) and X is the value shown
>in the boot log, then we may need to tweak things a bit further in the
>code that tries to guestimate max permitted dom0 size.
>
>
>> 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