All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Duffy <cduffy@spamcop.net>
To: xen-devel@lists.xensource.com
Subject: DomU Oopsing on xen-3.0-testing changeset 8259
Date: Fri, 23 Dec 2005 13:03:22 -0600	[thread overview]
Message-ID: <dohhlq$476$1@sea.gmane.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 508 bytes --]

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).

[-- Attachment #2: xen-oops --]
[-- Type: text/plain, Size: 1530 bytes --]

Unable to handle kernel NULL pointer dereference at 0000000000000a33 RIP:
<ffffffff8013e0a3>{__dequeue_signal+275}
PGD 11146067 PUD 185ee067 PMD 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in: ipv6 dm_mod
Pid: 2642, comm: java Tainted: GF     2.6.12.6-xenU
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} <ffffffff80140a1d>{sys_rt_sigtimedwait+589}
       <ffffffff80140d93>{sys_tgkill+291} <ffffffff801403cd>{sigprocmask+253}
       <ffffffff801404d3>{sys_rt_sigprocmask+211} <ffffffff80112406>{system_call+134}
       <ffffffff80112380>{system_call+0}

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 #3: config-2.6.12.6-xen0.bz2 --]
[-- Type: application/octet-stream, Size: 7761 bytes --]

[-- Attachment #4: config-2.6.12.6-xenU.bz2 --]
[-- Type: application/octet-stream, Size: 4522 bytes --]

[-- Attachment #5: Type: text/plain, Size: 138 bytes --]

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

             reply	other threads:[~2005-12-23 19:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-23 19:03 Charles Duffy [this message]
2006-06-19 13:12 ` Oops in xen 3.0.2 dequeue_signal [was: Re: DomU Oopsing on xen-3.0-testing changeset 8259] Charles Duffy
2006-06-19 13:59   ` Keir Fraser
2006-06-26 21:15     ` Charles Duffy
2006-07-18 20:20     ` Charles Duffy
2006-06-19 14:00   ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='dohhlq$476$1@sea.gmane.org' \
    --to=cduffy@spamcop.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.