From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756903AbYHYTq6 (ORCPT ); Mon, 25 Aug 2008 15:46:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753905AbYHYTqu (ORCPT ); Mon, 25 Aug 2008 15:46:50 -0400 Received: from mtaout01-winn.ispmail.ntl.com ([81.103.221.47]:50832 "EHLO mtaout01-winn.ispmail.ntl.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753685AbYHYTqu (ORCPT ); Mon, 25 Aug 2008 15:46:50 -0400 From: Ian Campbell To: Jeremy Fitzhardinge Cc: Sally-Anne Edwards , linux-kernel@vger.kernel.org In-Reply-To: <48B3099E.3060407@goop.org> References: <39fd98ca0808240801x7edbe0e6gf242f08de88cd92c@mail.gmail.com> <39fd98ca0808240804p454faff9u289abfc074dbea3@mail.gmail.com> <48B3099E.3060407@goop.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-L5jQEnYYhYFrV/62Dhuz" Date: Mon, 25 Aug 2008 20:46:41 +0100 Message-Id: <1219693601.27921.172.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 X-SA-Exim-Connect-IP: 192.168.1.5 X-SA-Exim-Mail-From: ijc@hellion.org.uk Subject: Re: Fwd: domU lenny not working: BUG: unable to handle kernel paging request at e7437cc0 X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on hopkins.hellion.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-L5jQEnYYhYFrV/62Dhuz Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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: >=20 > bret =3D RING_GET_RESPONSE(&info->ring, i); > id =3D bret->id; > req =3D (struct request *)info->shadow[id].request; >=20 > which suggests the backend driver is passing back a bogus request ID. >=20 > 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/). 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//device/vbd//protocol x86_3= 2-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. --=20 Ian Campbell Success is getting what you want; happiness is wanting what you get. --=-L5jQEnYYhYFrV/62Dhuz Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkizDCAACgkQM0+0qS9rzVnjXwCgr7QSIyHIkN8ZZrkJp3ivQvb7 8MsAoOjBsc+lJwZlaW/kl3+owJv511ia =Cbeq -----END PGP SIGNATURE----- --=-L5jQEnYYhYFrV/62Dhuz--