xen-unstable.hg's 15693:87a72ba32301ceb894e065d760953aa98730c0cd,
"[IA64] Saner dom0 memory and cpu defaults" seems to cause a regression
on my HP RX2620 with 2Gb of memory.
I can get around this pretty easily by specifying dom0_mem on the
command line. Emirically I have found that values of 1021M or less
boot, while values of 1022M or more fail. This seems substantially
smaller than the 1926M that xen calculates could be used, though that
figure does seem to correlate with the 2G of physical memory that the
machine has.
Let me know what I should poke to investigate further.
__ __ _____ ___ _ _ _
\ \/ /___ _ __ |___ / / _ \ _ _ _ __ ___| |_ __ _| |__ | | ___
\ // _ \ '_ \ |_ \| | | |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
/ \ __/ | | | ___) | |_| |__| |_| | | | \__ \ || (_| | |_) | | __/
/_/\_\___|_| |_| |____(_)___/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0-unstable (horms@xxxxxxxxxxxxxxxxxxx) (gcc version 3.4.5) Tue
Aug 28 18:48:34 JST 2007
Latest ChangeSet: Thu Aug 16 13:46:50 2007 -0600 15760:049d4baa9965
(XEN) Console output is synchronous.
(XEN) Xen command line: BOOT_IMAGE=net0:ia64/people/horms/vmlinux-xen
sync_console conswitch=bb
(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=101fff8
(XEN) Before xen_heap_start: f0000000041b5eb0
(XEN) After xen_heap_start: f0000000043c0000
(XEN) Init boot pages: 0x10000c0 -> 0x4000000.
(XEN) Init boot pages: 0x8000000 -> 0x3e874000.
(XEN) Init boot pages: 0x3eb90000 -> 0x3ee78000.
(XEN) Init boot pages: 0x3fc00000 -> 0x3fe28000.
(XEN) Init boot pages: 0x4040000000 -> 0x407d1b4010.
(XEN) Init boot pages: 0x407d1b4070 -> 0x407d1b7f8b.
(XEN) Init boot pages: 0x407d1b7fd5 -> 0x407d1bb000.
(XEN) Init boot pages: 0x407d6c4528 -> 0x407d6c5000.
(XEN) Init boot pages: 0x407df95fe3 -> 0x407ef9c010.
(XEN) Init boot pages: 0x407ef9c880 -> 0x407effc000.
(XEN) Init boot pages: 0x407f000000 -> 0x407fca8000.
(XEN) Init boot pages: 0x407fd14000 -> 0x407fe04000.
(XEN) Init boot pages: 0x407fe80000 -> 0x407ffe0000.
(XEN) System RAM: 2012MB (2060768kB)
(XEN) size of virtual frame_table: 5120kB
(XEN) virtual machine to physical table: f6fffffff7f00040 size: 1072kB
(XEN) max_page: 0x101fff8
(XEN) allocating frame table/mpt table at mfn 0.
(XEN) Xen heap: 60MB (61696kB)
(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) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Time init:
(XEN) .... System Time: 1531658ns
(XEN) .... scale: 2DB695F11
(XEN) num_online_cpus=1, max_cpus=64
(XEN) Brought up 2 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: 1926MB
(XEN) Reducing dom0 memory allocation from 4194304K to 1973040K to fit
available memory
(XEN) Dom0 kernel: 64-bit, lsb, paddr 0x4000000 -> 0x4620d50
(XEN) METAPHYSICAL MEMORY ARRANGEMENT:
(XEN) Kernel image: 4000000->4620d50
(XEN) Entry address: 400ff20
(XEN) Init. ramdisk: 4628000 len 8d0fe3
(XEN) Start info.: 4624000->4628000
(XEN) Dom0 max_vcpus=2
(XEN) Dom0: 0xf000000007ab4080
(XEN) enable lsapic entry: 0xf00000003fe37b28
(XEN) enable lsapic entry: 0xf00000003fe37b40
(XEN) Domain0 EFI passthrough: ACPI 2.0=0x3fe2c000 SMBIOS=0x3ee7c000
(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) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) 3... 2... 1...
(XEN) *** Serial input -> DOM0 (type 'CTRL-b' 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
displayed once)
Linux version 2.6.18 (horms@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 3.4.5)
#110 SMP Tue Aug 28 18:47:33 JST 2007
EFI v1.00 by Xen/ia64: SALsystab=0x2178 ACPI 2.0=0x3fe2c000 SMBIOS=0x3ee7c000
Initial ramdisk at: 0xe000000004628000 (9244643 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
GSI 36 (level, low) -> CPU 0 (0x0000) vector 49
2 CPUs available, 4 CPUs total
Running on Xen! start_info_pfn=0x1189 nr_pages=123315 flags=0x3
MCA related initialization done
SMP: Allowing 4 CPUs, 2 hotplug CPUs
Built 1 zonelists. Total pages: 16901120
Kernel command line: NAME=rx2620 console=tty0 console=ttyS0,115200n8 ip=on ro
PID hash table entries: 4096 (order: 12, 32768 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 67108864 (order: 15, 536870912 bytes)
Inode-cache hash table entries: 33554432 (order: 14, 268435456 bytes)
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 : [<a000000100125c41>] Not
tainted
ip is at kmem_cache_alloc+0xe1/0x2a0
unat: 0000000000000000 pfs : 4000000000000793 rsc : 0000000000000007
rnat: 0000000000000000 bsps: 0000000000000000 pr : 0000000000006989
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f
csd : 0000000000000000 ssd : 0000000000000000
b0 : a000000100049940 b6 : a00000010004a720 b7 : a000000100014750
f6 : 1003e5c1d6f7a17bb97ec f7 : 1003e9e3779b97f4a7c16
f8 : 1003e0a00000010003ba2 f9 : 1003e000000000000007f
f10 : 1003e0000000000000379 f11 : 1003e6db6db6db6db6db7
r1 : a0000001006eb6c0 r2 : 0000000000000001 r3 : fffffffffff00001
r8 : fffffffffff04c18 r9 : 0000000000000000 r10 : 0000000000000001
r11 : 0000000000000000 r12 : a00000010040b6b0 r13 : a000000100404000
r14 : 0000000000000001 r15 : fffffffffff00001 r16 : 0000000000000000
r17 : 0000000000000000 r18 : a000000100476c88 r19 : 0000000000000000
r20 : a000000100404f34 r21 : 000000007fffffff r22 : 0000000000000000
r23 : a00000010003ba20 r24 : a00000010003ba00 r25 : a000000100000000
r26 : a0000001004852c0 r27 : a0000001004ec158 r28 : a00000010047dff0
r29 : a00000010047dfe0 r30 : 00000000000001e4 r31 : 000000000003ba40
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home