All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
	Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: Stock 2.6.27 kernel hanging on WP test
Date: Mon, 12 Oct 2009 09:14:20 -0700	[thread overview]
Message-ID: <4AD355DC.8060901@goop.org> (raw)
In-Reply-To: <4ACE6E2A.1050104@goop.org>

On 10/08/09 15:56, Jeremy Fitzhardinge wrote:
> On 10/08/09 15:32, Jeremy Fitzhardinge wrote:
>   
>> When I boot Fedora 9 with a stock 2.7.26.25 32-bit-PAE kernel, it's
>> hanging forever in the WP test.  I'm running current xen-unstable
>> 1d7221667204.
>>
>> Another kernel (I think non-PAE this time) complained that the WP test
>> failed (ie, supervisor was allowed to write to a RO page without fault).
>>
>> The previous version of Xen I tried (only a couple of days ago), crashed
>> with "(XEN) Assertion 'v->arch.paging.mode' failed at multi.c:4069" when
>> starting the same domain, but I'm not sure if it got to the same point.
>>   
>>     
> Oh, I guess I should have pointed out this is an HVM domain.  PV is no
> problem.
>
> A 64-bit HVM Linux guest seems to die very quickly, but I'm not sure
> where its dying (I don't think 64-bit kernels bother testing for WP, so
> it could be another crash with the same root cause).
>   

Any thoughts about this?  When I look at the domain context with
debug-key 'd', the eip is on the write to the RO page doing the WP test,
and the VCPU is stuck in run state.  It looks like the Xen fault handler
is endlessly restarting the instruction rather than injecting a guest fault.

Presumably that path must mostly work or not much would run at all.  The
only thing that occurs to me is that some heuristic is putting Xen down
some unusual path that has a bug in it.  The fault is a bit unusual
because it's a deliberate write to a RO fixmap slot, high in the 32-bit
address space.

    J

  reply	other threads:[~2009-10-12 16:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 22:32 Stock 2.6.27 kernel hanging on WP test Jeremy Fitzhardinge
2009-10-08 22:56 ` Jeremy Fitzhardinge
2009-10-12 16:14   ` Jeremy Fitzhardinge [this message]
2009-10-13 12:18 ` Gianluca Guida
2009-10-13 12:24   ` Gianluca Guida

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=4AD355DC.8060901@goop.org \
    --to=jeremy@goop.org \
    --cc=Tim.Deegan@citrix.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.