I make a new domain0 kernel with CONFIG_IA64_DIG .It still panic.
The log looks like:
Xen version 3.0-unstable (build@) (gcc version 3.4.6 20060404 (Red Hat
3.4.6-3)) Mon Aug 13 05:01:50 CST 2007
Latest ChangeSet: Sun Aug 12 12:19:13 2007 -0600 15696:5b19839d0365
07/24/07 02:14p 6,444,451 vmlinuz.gz
(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=7ffed
(XEN) Before xen_heap_start: f0000000041c6cb0
(XEN) After xen_heap_start: f0000000041dc000
(XEN) Init boot pages: 0x10000c0 -> 0x4000000.
(XEN) Init boot pages: 0x8000000 -> 0x7f708000.
(XEN) Init boot pages: 0x7fe58000 -> 0x7ff30000.
(XEN) Init boot pages: 0x180000000 -> 0x1fd6a3000.
(XEN) Init boot pages: 0x1fe5fd6b0 -> 0x1fec14010.
(XEN) Init boot pages: 0x1fec14070 -> 0x1fec17f8e.
(XEN) Init boot pages: 0x1fec17fc2 -> 0x1fec1a000.
(XEN) Init boot pages: 0x1fef4131e -> 0x1fef4c010.
(XEN) Init boot pages: 0x1fef4c8e0 -> 0x1ffe10000.
(XEN) Init boot pages: 0x1ffe80000 -> 0x1fffb4000.
(XEN) System RAM: 4071MB (4168848kB)
(XEN) size of virtual frame_table: 10240kB
(XEN) virtual machine to physical table: f6ffffffffc00098 size: 2080kB
(XEN) max_page: 0x7ffed
(XEN) allocating frame table/mpt table at mfn 0.
(XEN) Xen heap: 62MB (63632kB)
(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: 3085033ns
(XEN) .... scale: 2DD6BDFD5
(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: 3973MB
(XEN) Reducing dom0 memory allocation from 4194304K to 4068672K to fit
available memory
(XEN) Dom0 kernel: 64-bit, lsb, paddr 0x4000000 -> 0x5385628
(XEN) METAPHYSICAL MEMORY ARRANGEMENT:
(XEN) Kernel image: 4000000->5385628
(XEN) Entry address: 400ff20
(XEN) Init. ramdisk: 538c000 len 32731e
(XEN) Start info.: 5388000->538c000
(XEN) Dom0 max_vcpus=2
(XEN) Dom0: 0xf000000007cd4080
(XEN) enable lsapic entry: 0xf00000007ff8325c
(XEN) enable lsapic entry: 0xf00000007ff8328c
(XEN) ACPI_INTERRUPT_CPEI disabled for Domain0
(XEN) Domain0 EFI passthrough: MPS=0x7ff82000 ACPI 2.0=0x7ff83000
ACPI=0x7ff84000 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 displayed once)
(XEN) WARN: GSI 3 in use by Xen.
Linux version 2.6.18-xen (ronghui@vti-build) (gcc version 4.1.1) #1 SMP
Thu Aug 30 12:20:07 CST 2007
EFI v1.00 by Xen/ia64: SALsystab=0x2178 MPS=0x7ff82000 ACPI
2.0=0x7ff83000 ACPI=0x7ff84000 SMBIOS=0xf0000
booting generic kernel on platform dig
Initial ramdisk at: 0xe00000000538c000 (3306270 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
2 CPUs available, 16 CPUs total
Running on Xen! start_info_pfn=0x14e2 nr_pages=254292 flags=0x3
Virtual mem_map starts at 0xa0007ffffe470000
SMP: Allowing 16 CPUs, 14 hotplug CPUs
Built 1 zonelists. Total pages: 250954
Kernel command line: nomca console=tty0 console=ttyS0,57600,8n1
root=/dev/VolGroup00/LogVol00 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 : [<a00000010012c531>]
Not tainted
ip is at kmem_cache_alloc+0x131/0x2c0
unat: 0000000000000000 pfs : 4000000000000610 rsc : 0000000000000007
rnat: 0000000000000000 bsps: 0000000000000000 pr : 0000000000009989
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f
csd : 0000000000000000 ssd : 0000000000000000
b0 : a00000010004b8f0 b6 : a00000010004bb40 b7 : a000000100014d70
f6 : 1003eee559c2687d4f864 f7 : 1003e9e3779b97f4a7c16
f8 : 1003e0a00000010003dd6 f9 : 000000000000000000000
f10 : 000000000000000000000 f11 : 000000000000000000000
r1 : a0000001011225a0 r2 : a000000100f23c58 r3 : 0000000000000001
r8 : fffffffffff00001 r9 : fffffffffff04c18 r10 : 0000000000000000
r11 : 0000000000000000 r12 : a000000100ce36a0 r13 : a000000100cdc000
r14 : 0000000000000001 r15 : fffffffffff00001 r16 : 0000000000000000
r17 : 0000000012000000 r18 : a000000100cdc018 r19 : a000000100ce3710
r20 : 0000000000000000 r21 : 0000000000000000 r22 : 0000000000000000
r23 : a000000100cdcf24 r24 : 0000000000000000 r25 : 0000000000000006
r26 : a000000100ce3714 r27 : a000000100ce3720 r28 : 0000000000000000
r29 : a000000100f2d1f8 r30 : a000000100ce3718 r31 : 000000007fffffff
-----Original Message-----
From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jarod
Wilson
Sent: Tuesday, August 28, 2007 10:48 PM
To: xen-ia64-devel
Subject: Re: [Xen-ia64-devel] Regression: [IA64] Saner dom0 memory and
cpudefaults
Alex Williamson wrote:
> On Tue, 2007-08-28 at 19:28 +0900, Horms wrote:
>> 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.
>
> Are you booting a CONFIG_IA64_DIG kernel? Thanks,
This looks to be exactly the same thing Zhang is hitting. Zhang, can you
also confirm whether or not you've built your kernel with
CONFIG_IA64_DIG?
All my own testing has been with kernels built w/CONFIG_IA64_GENERIC,
which I'm pretty sure also worked on an HP rx2620 here, and definitely
works on an HP rx2660, rx6600, rx8620, rx8640, zx2000 and a Hitachi
ColdFusion 3e/Intel s6e4533 system.
--
Jarod Wilson
jwilson@xxxxxxxxxx
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home