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


[Xen-users] xen-unstable amd64 troubles

To: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] xen-unstable amd64 troubles
From: Thomas Schneider <etomsch@xxxxxxxxxx>
Date: Thu, 10 Nov 2005 17:03:34 +0100
Delivery-date: Thu, 10 Nov 2005 16:03:43 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I'm using xen-unstable with all the latest changesets and some domains on it on a amd64 machine.
Today my domains crashed with the following output:

Unable to handle kernel paging request at ffff88000e928700 RIP:
PGD 788067 PUD 789067 PMD 7fe067 PTE 0
Oops: 0002 [1]
Pid: 0, comm: swapper Not tainted
RIP: e030:[<ffffffff803988ca>] <ffffffff803988ca>{netif_poll+1354}
RSP: e02b:ffffffff806d3d98  EFLAGS: 00010212
RAX: ffff88000e928700 RBX: ffff88000e909940 RCX: ffff88000e928058
RDX: ffff88000e928700 RSI: ffff88000e9091c0 RDI: ffff88000e909940
RBP: ffff88000e909940 R08: 0000000000feffff R09: 0000000000000017
R10: ffff88000f312250 R11: 0000000000000001 R12: ffff8800016d4360
R13: ffff88000167c550 R14: 00000000000000c0 R15: 0000000000000000
FS:  0000000000505ae0(0000) GS:ffffffff806c0080(0000) knlGS:ffffffff80600400
CS:  e033 DS: 0000 ES: 0000
Process swapper (pid: 0, threadinfo ffffffff806d2000, task ffffffff8057d500)
Stack: 0000000180117076 0000000200000040 0000000000000002 001e7cab001e7cab
      ffffffff806d3e2c ffff8800016d4000 ffffffff806d3dc8 ffffffff806d3dc8
      ffff880000000000 ffff8800016d4000
Call Trace:<ffffffff803ea348>{net_rx_action+152} <ffffffff801325ab>{__do_softirq+107}
      <ffffffff8013264d>{do_softirq+61} <ffffffff80114ea9>{do_IRQ+57}
<ffffffff8010d948>{evtchn_do_upcall+136} <ffffffff80112029>{do_hypervisor_callback+17}
      <ffffffff8010fa53>{xen_idle+83} <ffffffff8010fa53>{xen_idle+83}
      <ffffffff8010fa8f>{cpu_idle+31} <ffffffff806d46ea>{start_kernel+490}

Code: c7 00 01 00 00 00 48 8b 83 10 01 00 00 c7 40 04 00 00 00 00
RIP <ffffffff803988ca>{netif_poll+1354} RSP <ffffffff806d3d98>
CR2: ffff88000e928700
<0>Kernel panic - not syncing: Aiee, killing interrupt handler!

xm dmesg tells me:

(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen).
(XEN) gnttab_transfer: invalid pfn for mfn=4f27e001
(XEN) gnttab_transfer: invalid pfn for mfn=3f7df001
(XEN) gnttab_transfer: invalid pfn for mfn=3f03b001
(XEN) gnttab_transfer: invalid pfn for mfn=516ca001
(XEN) gnttab_transfer: invalid pfn for mfn=4f306001
(XEN) gnttab_transfer: invalid pfn for mfn=50cf0001
(XEN) gnttab_transfer: invalid pfn for mfn=52305001
(XEN) gnttab_transfer: invalid pfn for mfn=510ce001
(XEN) gnttab_transfer: invalid pfn for mfn=3efc1001
(XEN) gnttab_transfer: invalid pfn for mfn=3efc2001
(XEN) gnttab_transfer: invalid pfn for mfn=3efc3001
(XEN) gnttab_transfer: invalid pfn for mfn=4e74c001
(XEN) gnttab_transfer: invalid pfn for mfn=4e74d001
(XEN) gnttab_transfer: invalid pfn for mfn=4e74e001

except from that there's nothing unusual in any logs/debug-outputs.

Could anyone please explain to me, what could be done here?

Thanks in advance,


-- So Long, and Thanks for all the Fish
            - Douglas Adams, Hitchhikers Guide to the Galaxy --

Xen-users mailing list

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