From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jed Smith <jsmith@linode.com>
Cc: xen devel <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Re: [pv_ops domU] 2.6.30.5 - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update
Date: Thu, 20 Aug 2009 16:31:59 -0700 [thread overview]
Message-ID: <4A8DDCEF.9020303@goop.org> (raw)
In-Reply-To: <4A8D9FC7.7070101@linode.com>
On 08/20/09 12:11, Jed Smith wrote:
> Jeremy Fitzhardinge wrote:
>
>>>> Is it new with 2.6.30.5?
>>>>
> Perhaps earlier, and we're just now running into it. I am able to
> reproduce on the v2.6.30 release. My initial bisect leads me here (from
> bad=v2.6.30 and good=v2.6.29 in linux-2.6.git):
>
> commit 9049a11de73d3ecc623f1903100d099f82ede56c
> Merge: c47c1b1 e4d0407
> Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> Date: Wed Feb 11 11:52:22 2009 -0800
>
> Merge commit 'remotes/tip/x86/paravirt' into x86/untangle2
>
> I note astutely, however, that's a pretty large merge commit.
>
Yeah. If it shows up in that merge, then obviously it must be one of
the constituent changes which is provoking the problem, unless there's
something about the merge itself.
Just to double check, can to test the two parents,
c47c1b1f3a9d6973108020df1dcab7604f7774dd and
e4d0407185cdbdcfd99fc23bde2e5454bbc46329, to see if one or both exhibits
the problem?
I see your bisect tested c47c1b1f3a9 as OK, so try e4d0407185.
J
next prev parent reply other threads:[~2009-08-20 23:31 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
2009-08-18 20:56 ` Jeremy Fitzhardinge
2009-08-20 19:11 ` Jed Smith
2009-08-20 23:31 ` Jeremy Fitzhardinge [this message]
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=4A8DDCEF.9020303@goop.org \
--to=jeremy@goop.org \
--cc=jsmith@linode.com \
--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.