From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: xen devel <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [pv_ops domU] 2.6.30.5 - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update
Date: Tue, 18 Aug 2009 13:15:14 -0700 [thread overview]
Message-ID: <4A8B0BD2.2060304@goop.org> (raw)
In-Reply-To: <4A8AB7B8.4070905@theshore.net>
On 08/18/09 07:16, Christopher S. Aker wrote:
> Jeremy Fitzhardinge wrote:
>> Does this happen every time, sometimes or just once?
>
> Completely reproducible, however I was wrong about the Xen version -
> it is 3.2.1-rc5. FWIW, I'm unable to reproduce this on a dev box
> running 3.4.1.
That's curious. Keir, do you know of any bugs which could cause domU
misbehaviour like this?
> I haven't tried any other Xen versions (we have many running).
>
>> Is it new with 2.6.30.5?
>
> Yes. The last pv_ops kernel we ran was 2.6.29.
Have you tried any other distros? I'll try to repro with a current Xen
and my Fedora system.
It would be helpful if you could try 2.6.30/.[1-4] as well to see if the
problem arises. I'm trying a bisection myself, but it sounds like I
shouldn't be able to repo it.
J
next prev parent reply other threads:[~2009-08-18 20:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 0:26 [pv_ops domU] 2.6.30.5 - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update Christopher S. Aker
2009-08-18 4:30 ` Jeremy Fitzhardinge
2009-08-18 14:16 ` Christopher S. Aker
2009-08-18 20:15 ` Jeremy Fitzhardinge [this message]
2009-08-18 20:56 ` Jeremy Fitzhardinge
2009-08-20 19:11 ` Jed Smith
2009-08-20 23:31 ` Jeremy Fitzhardinge
2009-08-21 0:13 ` Jed Smith
2009-08-21 0:38 ` Jeremy Fitzhardinge
2009-08-21 14:57 ` Jed Smith
2009-08-21 16:20 ` Jeremy Fitzhardinge
2009-08-21 16:30 ` Jed Smith
2009-08-21 16:16 ` Jeremy Fitzhardinge
2009-08-21 17:02 ` Jed Smith
2009-08-21 17:44 ` Jeremy Fitzhardinge
2009-08-21 16:16 ` Jeremy Fitzhardinge
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=4A8B0BD2.2060304@goop.org \
--to=jeremy@goop.org \
--cc=caker@theshore.net \
--cc=keir.fraser@eu.citrix.com \
--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.