WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Crash during boot in Debian lenny default dom0 kernel (2

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686)
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Thu, 25 Feb 2010 11:46:21 +0000
Cc: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>, Yunhong Jiang <yunhong.jiang@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 25 Feb 2010 03:47:21 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=Mr9vJvhsvBlnkBSkrKSjLLbahEzaIV/2Izfqd+Dy8JQ=; b=DIiL4zM8/XGegF3viAg3Zp6B9GUBX04Ywl2mh4fef8X7coCuEX59ujY3u8TI4QZxzX H/x9GPbQ8eulxJTu7GTdE5gRK3o5tUPBRE77dtVmPPgiiNp1LfmHRfU7QwW8X9mylnjx 4Of79v7f4b2jQy83EGhS5AQbbs0oHNYDtQHHc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=fiOZFhd1IQMdglz13KPodXLObGB6Bby89DG3GjjYEFrWktN7Qy9lIB1bJpAKkbqgOm 8oHklVWmZDrzkPoJoxRNMG9/5cZylJxNTcNkFnG9IGGWSTG1IxQ0fKAScSUF3sZ/gcCq d8ctQohQfKCZzlwQnrylQao1OkobLqGIVOtOI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B8665680200007800031406@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <de76405a1002241047w4d138abbjc872c371c0e742ed@xxxxxxxxxxxxxx> <25841307.20100224200810@xxxxxxxxxxxxxx> <20100224202009.GE2761@xxxxxxxxxxx> <de76405a1002241557y4449110v37b811fd36c60c4d@xxxxxxxxxxxxxx> <C8EDE645B81E5141A8C6B2F73FD92651247A93D81D@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <de76405a1002250248wcc16101v644f409f73dd43b1@xxxxxxxxxxxxxx> <4B8665680200007800031406@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I'm looking at the debian source package for this kernel to see if I
can sort out where it got the header from.

Given that this is already in a major distribution, is there any way
we can fail gracefully if someone's running this kernel?  I'm not
familiar enough with the MSI to know if this is possible, or what a
good set of "sanity checks" would be for failing the hypercall.

 -George

On Thu, Feb 25, 2010 at 10:56 AM, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:
>>>> George Dunlap <George.Dunlap@xxxxxxxxxxxxx> 25.02.10 11:48 >>>
>>Is it possible that there's actually a bug in the compat code, and
>>that table_base actually *was* set to (uint32_t)1?  If a reasonable
>>number for table_base is "1", giving it 64 bits in the structure would
>>seem a bit like overkill...
>
> "1" definitely is not a reasonable value here. And it's also not the
> compat code I'm sure - it is the kernel using a bad structure definition.
>
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>