From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Xen 4.0 crashes with pvops kernel Date: Tue, 15 Jun 2010 16:21:26 +0100 Message-ID: <4C17B69602000078000068F3@vpn.id2.novell.com> References: <4C17932F0200007800006821@vpn.id2.novell.com> <4C179A47020000780000683A@vpn.id2.novell.com> <4C179FBC020000780000685D@vpn.id2.novell.com> <4C17A6B002000078000068A3@vpn.id2.novell.com> <4C17B15002000078000068D5@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Cris Daniluk Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org >>> On 15.06.10 at 17:01, Cris Daniluk wrote: > On Tue, Jun 15, 2010 at 10:58 AM, Jan Beulich = wrote: >>>>> On 15.06.10 at 16:35, Cris Daniluk wrote: >>> Hmm, so could there be a Xen-based workaround in the interim, such as >>> bypassing the code page that is triggering this? It seems like that >>> may not provide too much relief given the nature of the issue. >> >> Unfortunately I can't think of anything. >> >> Jan >> >=20 > Fair enough. I will see if I can get some other hardware to test with. > What would the path toward resolution be here? It still seems like Xen > shouldn't be writing into that page, let alone reading.. I can't think of anything but getting the BIOS fixed, plus getting handling in proper shape in the kernel. Jan