From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
xen devel <xen-devel@lists.xensource.com>
Subject: Re: 2.6.32.27 dom0 - BUG: unable to handle kernel paging request
Date: Mon, 31 Jan 2011 14:25:40 -0800 [thread overview]
Message-ID: <4D4736E4.6090806@goop.org> (raw)
In-Reply-To: <4D472486.9050205@theshore.net>
On 01/31/2011 01:07 PM, Christopher S. Aker wrote:
>> Xen: 3.4.4-rc1-pre 64bit (xenbits @ 19986)
> > Dom0: 2.6.32.27-1 PAE (xen/stable-2.6.32.x)
>>
>> We've been running our xen-thrash testsuite on a bunch of hosts
>> against a very recent build, and we've just hit this on one box:
>>
>> BUG: unable to handle kernel paging request at 15555d60
>
> Two additional boxes out of my last test round have also hit this.
> About one a week.
>
> Ian / Jeremy: Where do I go from here?
It's also not impossible this bug is related to the "get_user_pages" bug
that has been discussed over the last few days. I need to think about
that too.
J
next prev parent reply other threads:[~2011-01-31 22:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 22:57 2.6.32.27 dom0 - BUG: unable to handle kernel paging request Christopher S. Aker
2010-12-31 1:29 ` Jeremy Fitzhardinge
2010-12-31 17:19 ` Christopher S. Aker
2011-01-02 20:08 ` Christopher S. Aker
2011-01-04 9:16 ` Ian Campbell
2011-01-04 20:30 ` Christopher S. Aker
2011-01-04 20:34 ` Ian Campbell
2011-01-04 21:59 ` Christopher S. Aker
2011-01-09 18:07 ` Christopher S. Aker
2011-01-10 18:56 ` Konrad Rzeszutek Wilk
2011-01-10 21:49 ` John Weekes
2011-01-15 15:57 ` Christopher S. Aker
2011-01-31 21:07 ` Christopher S. Aker
2011-01-31 21:17 ` Konrad Rzeszutek Wilk
2011-01-31 22:19 ` Jeremy Fitzhardinge
2011-01-31 22:22 ` Jeremy Fitzhardinge
2011-01-31 22:25 ` Jeremy Fitzhardinge [this message]
2011-02-14 23:52 ` Christopher S. Aker
2011-02-15 0:19 ` Jeremy Fitzhardinge
2011-02-15 1:15 ` Christopher S. Aker
2011-01-13 14:43 ` Konrad Rzeszutek Wilk
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=4D4736E4.6090806@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=caker@theshore.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.