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: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
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: Fri, 26 Feb 2010 11:21:14 +0000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Yunhong Jiang <yunhong.jiang@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Fri, 26 Feb 2010 03:21:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <383241072.20100226121430@xxxxxxxxxxxxxx>
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> <20100224202009.GE2761@xxxxxxxxxxx> <de76405a1002241557y4449110v37b811fd36c60c4d@xxxxxxxxxxxxxx> <C8EDE645B81E5141A8C6B2F73FD92651247A93D81D@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <de76405a1002250248wcc16101v644f409f73dd43b1@xxxxxxxxxxxxxx> <4B8665680200007800031406@xxxxxxxxxxxxxxxxxx> <de76405a1002250346q32cf093i58429407ccfb5f32@xxxxxxxxxxxxxx> <de76405a1002250413x31816283p61c2acec44b19fe3@xxxxxxxxxxxxxx> <4B868421020000780003145C@xxxxxxxxxxxxxxxxxx> <de76405a1002250528u6ad405c5y37d54d3ae58d4278@xxxxxxxxxxxxxx> <de76405a1002260305k1705f7cnd777472b86ca4378@xxxxxxxxxxxxxx> <383241072.20100226121430@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.23 (X11/20090817)
Do they? I've installed Lenny in 2 boxes recently (within the last 2 months), and neither has the pci=nomsi in the grub config. I'm pretty sure I would have remembered removing it. It's also not in the "xenkopt=" automagic kernel configuration.

I did install from a local mirror, but I've updated since then...

-George

Sander Eikelenboom wrote:
For what I remember from the past, the debian packages automatically put 
pci=nomsi in grub etc.
So perhaps it's wise to get that workaround removed as well.

--
Sander


Friday, February 26, 2010, 12:05:48 PM, you wrote:

OK, the attached patch fits cleanly in to the debian source package
infrastructure and can result in a built .deb file that actually
works.

Can those who know the system take a quick look to see if there's
anything obviously broken?  I'll file a bug report to debian with the
patch Monday; hopefully it will be picked up quickly.

Thanks,
 -George

On Thu, Feb 25, 2010 at 1:28 PM, George Dunlap
<George.Dunlap@xxxxxxxxxxxxx> wrote:
Forward porting the linux-2.6.18 patch has been straightforward so
far... I'm going to give it a spin and see if it actually boots. :-)

It's linux-2.6.18.hg c/s 645:359b1e70d9eb, in case you're interested.

 -George

On Thu, Feb 25, 2010 at 1:07 PM, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:
George Dunlap <George.Dunlap@xxxxxxxxxxxxx> 25.02.10 13:13 >>>
Any suggestions for a simple fix I can try to push upstream?
I'm afraid not (other than simply disabling at least the MSI-X part of
the code), as it would require table_base to be initialized properly.

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>