[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64



Puthiyaparambil, Aravindh wrote:
> With mem=3g dom0_mem=512M this is what happens...

How about non-debug xen? I also see similar problems with debug xen.

Jun
---
Intel Open Source Technology Center

> 
> Aravindh
> 
> (XEN) Truncating memory map to 3145728kB
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 000000000009dc00 (usable)
> (XEN)  000000000009dc00 - 00000000000a0000 (reserved)
> (XEN)  00000000000ce000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 0000000037ea0000 (usable)
> (XEN)  0000000037ea0000 - 0000000037edf000 (ACPI data)
> (XEN)  0000000037edf000 - 0000000037f00000 (ACPI NVS)
> (XEN)  0000000037f00000 - 00000000c0000000 (usable)
> (XEN) System RAM: 3071MB (3144948kB)
> (XEN) Xen heap: 14MB (14580kB)
> 
> ...................................
> 
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
>
'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xffffffff80000000,L
> OADER=generic'
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000060000000->0000000080000000
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80100000->ffffffff805cc086
> (XEN)  Init. ramdisk: ffffffff805cd000->ffffffff805cd000
> (XEN)  Phys-Mach map: ffffffff805cd000->ffffffff8064d000
> (XEN)  Page tables:   ffffffff8064d000->ffffffff80654000
> (XEN)  Start info:    ffffffff80654000->ffffffff80655000
> (XEN)  Boot stack:    ffffffff80655000->ffffffff80656000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff80800000
> (XEN)  ENTRY ADDRESS: ffffffff80100000
> (XEN) Scrubbing Free RAM: ...............................done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen).
> (XEN) (file=/root/xen/xen-unstable.hg/xen/include/asm/mm.h, line=204)
> Error pfn 7ffff: rd=ffff8300001c8080, od=0000000000000000,
> caf=00000000, taf=0000000000000000
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) CPU:    0
> (XEN) EIP:    e033:[<ffffffff8011e4a1>] ???
> (XEN) EFLAGS: 0000000000000282
> (XEN) rax: 00000000ffffffea   rbx: 00000000000001fe   rcx:
> ffffffff8011e49d   rdx: 0000000000000000
> (XEN) rsi: 0000000000000001   rdi: ffffffff80567e90   rbp:
> 0000000000802000   rsp: ffffffff80567e58
> (XEN) r8:  0000000000000004   r9:  0000000000000000   r10:
> 0000000000007ff0   r11: 0000000000000202
> (XEN) r12: ffffffff80802000   r13: ffffffff80568000   r14:
> ffffffff80105020   r15: ffffffff80105000
> (XEN) Guest stack trace from rsp=ffffffff80567e58:
> (XEN)    ffffffff8011e49d 0000000000000202 ffffffff8011e4a1
> 000000010000e030 0000000000010282 ffffffff80567e90 000000000000e02b
> 0000000060568008
> (XEN)    000000007ffff067 0000000000800000 ffffffff80592686
> 0000000000568000 0000000000000000 000000000000001b 0000000000000000
> 0000000020000000
> (XEN)    0000ffffffff8010 ffffffff80567fb0 ffffffff80592cd3
> 0000000000000000 0000000000000000 000000000000001b ffffffff805093bb
> ffffffff80567fa0
> (XEN)    0000ffffffff8010 ffffffff80567fb0 ffffffff8058eada
> 000000006064e830 ffffffff80502dbc 0000000000000001 0000000000060105
> 0000000000000000
> (XEN)    ffffffff80103000 ffffffff0000000f 0000000000010800
> ffffffff80452900 ffffffff80100038 00000000ffffffff 0000ffffffff8010
> ffffffff80567fb0
> (XEN)    ffffffff805884f8 ffffffff805093a0 ffffffff80588190
> 80108e0000100038 00000000ffffffff 0000000000000000 0000000000000000
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000
> (XEN) Domain 0 shutdown: rebooting machine.
> 
> 
> 
>> -----Original Message-----
>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
>> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Nakajima, Jun
>> Sent: Wednesday, August 10, 2005 2:25 PM
>> To: Puthiyaparambil, Aravindh; Keir Fraser
>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Davis, Jason; Magolan, John F;
>> Subrahmanian, Raj; Vessey, Bruce A
>> Subject: RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000
>> x86_64 
>> 
>> Puthiyaparambil, Aravindh wrote:
>>> Xen and Dom0 boots successfully on the Dell PowerEdge x86_64 box
>>> with Keir's new time fix. I did have to comment out the printk as
>>> suggested by Jun as the serial was getting flooded otherwise.
>>> 
>>> Jun, are you going to submit a patch for the map_alloc() function?
>>> 
>>> On the ES7000 x86_64 I no longer see the "Assertion 'tsc_elapsed32
>>> != 0'". But the system dies on the error shown at the end of the
>>> email. This is with changeset 6081 + Jun's map_alloc fix + Jerone's
>>> rm_nx patch. Any suggestions as to how to proceed?
>> 
>> Can you try to add mem=3g for the xen boot entry?
>> 
>> Jun
>> ---
>> Intel Open Source Technology Center
>> 
>>> 
>>> Thanks
>>> Aravindh




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.