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

["Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>]

Here is the disassembly output from vmlinux-syms-2.6.12.3-xen0. I am
wondering if I have a bad stack. The EIP points to 0xffffffff8011e4a1
<xen_l1_entry_update+113>:   ud2a

What does ud2a do?

Aravindh

Dump of assembler code from 0xffffffff8011e410 to 0xffffffff8011e4b0:
0xffffffff8011e410 <xen_l2_entry_update+112>:   (bad)
0xffffffff8011e411 <xen_l2_entry_update+113>:   ud2a
0xffffffff8011e413 <xen_l2_entry_update+115>:   enterq $0x3f30,$0x80
0xffffffff8011e417 <xen_l2_entry_update+119>:   (bad)
0xffffffff8011e418 <xen_l2_entry_update+120>:   (bad)
0xffffffff8011e419 <xen_l2_entry_update+121>:   (bad)
0xffffffff8011e41a <xen_l2_entry_update+122>:   decl   0x0(%rax)
0xffffffff8011e41d <xen_l2_entry_update+125>:   data16
0xffffffff8011e41e <xen_l2_entry_update+126>:   data16
0xffffffff8011e41f <xen_l2_entry_update+127>:   nop
0xffffffff8011e420 <xen_l2_entry_update+128>:   add    $0x18,%rsp
0xffffffff8011e424 <xen_l2_entry_update+132>:   retq
0xffffffff8011e425 <xen_l2_entry_update+133>:   data16
0xffffffff8011e426 <xen_l2_entry_update+134>:   data16
0xffffffff8011e427 <xen_l2_entry_update+135>:   data16
0xffffffff8011e428 <xen_l2_entry_update+136>:   nop
0xffffffff8011e429 <xen_l2_entry_update+137>:   data16
0xffffffff8011e42a <xen_l2_entry_update+138>:   data16
0xffffffff8011e42b <xen_l2_entry_update+139>:   data16
0xffffffff8011e42c <xen_l2_entry_update+140>:   nop
0xffffffff8011e42d <xen_l2_entry_update+141>:   data16
0xffffffff8011e42e <xen_l2_entry_update+142>:   data16
0xffffffff8011e42f <xen_l2_entry_update+143>:   nop
0xffffffff8011e430 <xen_l1_entry_update+0>:     mov
$0xffffffff7fffffff,%rax
0xffffffff8011e43a <xen_l1_entry_update+10>:    sub    $0x18,%rsp
0xffffffff8011e43e <xen_l1_entry_update+14>:    cmp    %rax,%rdi
0xffffffff8011e441 <xen_l1_entry_update+17>:    jbe
0xffffffff8011e450 <xen_l1_entry_update+32>
0xffffffff8011e443 <xen_l1_entry_update+19>:    mov    $0x80000000,%eax
0xffffffff8011e448 <xen_l1_entry_update+24>:    jmp
0xffffffff8011e45a <xen_l1_entry_update+42>
0xffffffff8011e44a <xen_l1_entry_update+26>:    data16
0xffffffff8011e44b <xen_l1_entry_update+27>:    data16
0xffffffff8011e44c <xen_l1_entry_update+28>:    nop
0xffffffff8011e44d <xen_l1_entry_update+29>:    data16
0xffffffff8011e44e <xen_l1_entry_update+30>:    data16
0xffffffff8011e44f <xen_l1_entry_update+31>:    nop
0xffffffff8011e450 <xen_l1_entry_update+32>:    mov
$0x780000000000,%rax
0xffffffff8011e45a <xen_l1_entry_update+42>:    lea
(%rax,%rdi,1),%rcx
0xffffffff8011e45e <xen_l1_entry_update+46>:    mov
4102811(%rip),%rdx        # 0xffffffff80507f00 <phys_to_machine_mapping>
0xffffffff8011e465 <xen_l1_entry_update+53>:    mov    %rsp,%rdi
0xffffffff8011e468 <xen_l1_entry_update+56>:    mov    %rcx,%rax
0xffffffff8011e46b <xen_l1_entry_update+59>:    and    $0xfff,%ecx
0xffffffff8011e471 <xen_l1_entry_update+65>:    shr    $0xc,%rax
0xffffffff8011e475 <xen_l1_entry_update+69>:    mov    %eax,%eax
0xffffffff8011e477 <xen_l1_entry_update+71>:    mov
(%rdx,%rax,4),%eax
0xffffffff8011e47a <xen_l1_entry_update+74>:    mov    %rsi,0x8(%rsp)
0xffffffff8011e47f <xen_l1_entry_update+79>:    mov    $0x1,%esi
0xffffffff8011e484 <xen_l1_entry_update+84>:    xor    %edx,%edx
0xffffffff8011e486 <xen_l1_entry_update+86>:    shl    $0xc,%rax
0xffffffff8011e48a <xen_l1_entry_update+90>:    or     %rcx,%rax
0xffffffff8011e48d <xen_l1_entry_update+93>:    mov    %rax,(%rsp)
0xffffffff8011e491 <xen_l1_entry_update+97>:    mov    %rsi,%rax
0xffffffff8011e494 <xen_l1_entry_update+100>:   mov    $0x7ff0,%r10
0xffffffff8011e49b <xen_l1_entry_update+107>:   syscall
0xffffffff8011e49d <xen_l1_entry_update+109>:   test   %eax,%eax
0xffffffff8011e49f <xen_l1_entry_update+111>:   jns
0xffffffff8011e4b0 <xen_l1_entry_update+128>
0xffffffff8011e4a1 <xen_l1_entry_update+113>:   ud2a
0xffffffff8011e4a3 <xen_l1_entry_update+115>:   enterq $0x3f30,$0x80
0xffffffff8011e4a7 <xen_l1_entry_update+119>:   (bad)
0xffffffff8011e4a8 <xen_l1_entry_update+120>:   (bad)
0xffffffff8011e4a9 <xen_l1_entry_update+121>:   (bad)
0xffffffff8011e4aa <xen_l1_entry_update+122>:   incl   0x0(%rax)
0xffffffff8011e4ad <xen_l1_entry_update+125>:   data16
0xffffffff8011e4ae <xen_l1_entry_update+126>:   data16
0xffffffff8011e4af <xen_l1_entry_update+127>:   nop


> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Puthiyaparambil, Aravindh
> Sent: Wednesday, August 10, 2005 2:36 PM
> To: Nakajima, Jun; 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
> 
> With mem=3g dom0_mem=512M this is what happens...
> 
> 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

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