From: Ian Campbell <ijc@hellion.org.uk>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Sally-Anne Edwards <sallyanne.edwards@googlemail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Fwd: domU lenny not working: BUG: unable to handle kernel paging request at e7437cc0
Date: Mon, 25 Aug 2008 20:46:41 +0100 [thread overview]
Message-ID: <1219693601.27921.172.camel@localhost.localdomain> (raw)
In-Reply-To: <48B3099E.3060407@goop.org>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
On Mon, 2008-08-25 at 12:35 -0700, Jeremy Fitzhardinge wrote:
> I haven't see this oops before, but I think the code in question
> correlates to:
>
> bret = RING_GET_RESPONSE(&info->ring, i);
> id = bret->id;
> req = (struct request *)info->shadow[id].request;
>
> which suggests the backend driver is passing back a bogus request ID.
>
> What's your host environment?
I believe it's a 64 bit Etch kernel running on a Lenny domain 0. I
wonder if that kernel doesn't write the protocol field in xenstore so
the 64 bit backend Sally-Anne is using cannot talk to the 32 bit
frontend correctly.
Sally, can you run xenstore-ls on the domain's path
(/local/domain/<domid>). Is there a protocol field in the vbd entry?
If not can you try starting the domain in the paused state (xm create
-p) and use xenstore-write to fill in the protocol node in the frontend
to "x86_32-abi". e.g.
xenstore write /local/domain/<domid>/device/vbd/<nr>/protocol x86_32-abi
before unpausing.
I thought the tools did this (so expected the Lenny tools to be correct)
but looking at the code it seems it is the domain 0 kernel which does
it.
Ian.
--
Ian Campbell
Success is getting what you want; happiness is wanting what you get.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-25 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39fd98ca0808240801x7edbe0e6gf242f08de88cd92c@mail.gmail.com>
2008-08-24 15:04 ` Sally-Anne Edwards
2008-08-25 19:35 ` Jeremy Fitzhardinge
2008-08-25 19:46 ` Ian Campbell [this message]
2008-08-25 20:22 ` Ian Campbell
2008-08-25 20:25 ` Jeremy Fitzhardinge
2008-08-25 20:54 ` Ian Campbell
2008-08-25 20:59 ` Jeremy Fitzhardinge
2008-08-26 6:06 ` Ian Campbell
2008-08-25 19:56 ` Sally-Anne Edwards
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=1219693601.27921.172.camel@localhost.localdomain \
--to=ijc@hellion.org.uk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sallyanne.edwards@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®