This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Wed, 10 Aug 2005 14:18:41 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Davis, Jason" <jason.davis@xxxxxxxxxx>, "Magolan, John F" <John.Magolan@xxxxxxxxxx>, "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>, "Vessey, Bruce A" <Bruce.Vessey@xxxxxxxxxx>
Delivery-date: Wed, 10 Aug 2005 18:18:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWdAZeo7cFZVA22QViz6u3TsjtZZwAR8SiAAAapuMAAAlRYsAAAp0YgABio7PA=
Thread-topic: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64
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?



(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 d9999: rd=ffff8300001da080, od=ffff8300001da080, caf=00000000,
(XEN) DOM0: (file=mm.c, line=1486) Error while validating pfn dffc7 for
type 0400000020000000. caf=80000004 taf=0400000020000001
(XEN) DOM0: (file=mm.c, line=1712) Error while pinning mfn dffc7
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) CPU:    0
(XEN) EIP:    e033:[<ffffffff8011e04c>] ???
(XEN) EFLAGS: 0000000000000282
(XEN) rax: 00000000ffffffea   rbx: 0000000007000000   rcx:
ffffffff8011e048   rdx: 0000000000000000
(XEN) rsi: 0000000000000001   rdi: ffffffff80567e70   rbp:
0000000020000000   rsp: ffffffff80567e38
(XEN) r8:  0000000000000200   r9:  0000000000000000   r10:
0000000000007ff0   r11: 0000000000000246
(XEN) r12: ffffffff808011b8   r13: 0000000000000037   r14:
ffffffff80800000   r15: 0000000000000000
(XEN) Guest stack trace from rsp=ffffffff80567e38:
(XEN)    ffffffff8011e048 0000000000000246 ffffffff8011e04c
000000010000e030 0000000000010282 ffffffff80567e70 000000000000e02b
(XEN)    00000000000dffc7 00000000dffff1b0 0000000007000000
0000000020000000 ffffffff80592be9 0000000000000000 0000000000839000
(XEN)    ffffffff80800000 ffff880020000000 ffff880000000000
ffff880020000000 0000780000000000 0000000080000000 ffffffff80592d81
(XEN)    0000000000000000 000000000000001b ffffffff805093bb
ffffffff80567fa0 0000ffffffff8010 ffffffff80567fb0 ffffffff8058eada
(XEN)    ffffffff80502dbc 0000000000000001 00000000000c0105
0000000000000000 ffffffff80103000 ffffffff0000000f 0000000000010800
(XEN)    ffffffff80100038 00000000ffffffff 0000ffffffff8010
ffffffff80567fb0 ffffffff805884f8 ffffffff805093a0 ffffffff80588190
(XEN)    00000000ffffffff 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000
(XEN) Domain 0 shutdown: rebooting machine.

> -----Original Message-----
> Try to use old version of arch/x86/time.c, for example, the one
> attached. You also might want to comment out:
> asmlinkage int do_page_fault(struct cpu_user_regs *regs)
> {
>     ...
> xen_fault:
>     if ( likely((fixup = search_exception_table(regs->eip)) != 0) )
>     {
>         perfc_incrc(copy_user_faults);
>         if ( !shadow_mode_enabled(d) )
>             //      DPRINTK("Page fault: %p -> %p\n", _p(regs->eip),
> _p(fixup));
>             ;
>         regs->eip = fixup;
>         return 0;
>     }
> Jun
> ---
> Intel Open Source Technology Center

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>