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] DomU Oopsing on xen-3.0-testing changeset 8259

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] DomU Oopsing on xen-3.0-testing changeset 8259
From: Charles Duffy <cduffy@xxxxxxxxxxx>
Date: Tue, 27 Dec 2005 09:04:15 -0600
Delivery-date: Tue, 27 Dec 2005 15:08:32 +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
User-agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
[Previously posted to the devel list; reposting to user, since there was no response there -- perhaps due to inappropriate context?]

One of my DomUs is sporadically oopsing, roughly once per day. This was
first observed on a pre-3.0-release changeset; after upgrading to
changeset 8259 on the xen-3.0-testing branch (after the release), it
still occurs.

This effectively kills the instance when it occurs -- worse, the
instance in question *stays* down even though panic=5 is specified as an
extra parameter to be passed to the DomU kernel.

The text of the oops is attached, as are my kernel configs (which are a
touch nonstandard).

Unable to handle kernel NULL pointer dereference at 0000000000000a33 RIP:
PGD 11146067 PUD 185ee067 PMD 0
Oops: 0000 [1] SMP
Modules linked in: ipv6 dm_mod
Pid: 2642, comm: java Tainted: GF
RIP: e030:[<ffffffff8013e0a3>] <ffffffff8013e0a3>{__dequeue_signal+275}
RSP: e02b:ffff88002aa1be58  EFLAGS: 00010046
RAX: 0000000000000a33 RBX: ffff880013d3fa88 RCX: 0000000000000009
RDX: 0000000000000200 RSI: 0000000000000a33 RDI: ffff880013d3fa88
RBP: ffff88003e680a30 R08: ffff88002aa1a000 R09: 0000000000000000
R10: 0000000000000060 R11: 0000000000000612 R12: 000000000000000a
R13: ffff88002aa1bec8 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000048c34960(0063) GS:ffffffff803e9d80(0000) knlGS:ffffffff803e9d80
CS:  e033 DS: 0000 ES: 0000
Process java (pid: 2642, threadinfo ffff88002aa1a000, task ffff880013d3f4b0)
Stack: 0000000000000000 ffff88002aa1bec0 ffff88002aa1bec8 ffff880013d3f4b0
       0000000000000000 ffffffff8013e1dd ffff88002aa1bed8 0000000000000000
       0000000000000000 7fffffffffffffff
Call Trace:<ffffffff8013e1dd>{dequeue_signal+45} 
       <ffffffff80140d93>{sys_tgkill+291} <ffffffff801403cd>{sigprocmask+253}

Code: 48 8b 00 0f 18 08 48 39 de 75 e2 48 85 ed 0f 84 84 00 00 00
RIP <ffffffff8013e0a3>{__dequeue_signal+275} RSP <ffff88002aa1be58>
CR2: 0000000000000a33

Attachment: config-
Description: Binary data

Attachment: config-
Description: Binary data

Xen-devel mailing list

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>