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] MSI badness in xen-unstable

To: Gianni Tedesco <gianni.tedesco@xxxxxxxxxx>
Subject: Re: [Xen-devel] MSI badness in xen-unstable
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Mon, 11 Oct 2010 14:05:09 -0700
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Mon, 11 Oct 2010 14:06:22 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=C4xEjbHzxMvx9nRdtTgq/sJUyqSQL8S79bTXob2m8wE=; b=cn5K+E4WJFHLs3gvJjjdjMwieBw659cGmf4A6yZUor/AJkEc57GXoJf109/W8U/N+f 4GZ6mDN7uMQLFxtDdc8PSYoh7ed4Y33ZQNgVWysobMdYH8ufHeMCnW9UcDS4c5ssYqiQ urlgAIkGR+m8ek+aIJwKnuQlIBEuyERD52i20=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=rTnF0DUUsuhRGdk/cG3ND/BlM38yRTflmd3J54qW93zlScKK11iZLisXwDcgveXPzN UrM/McjVSgtwJpfPh6sBr7C1NgCoRwQMOsttOdd+1zw5pN/m1X412cg7T2vmNXMLTpTf uA+IB0LvKNoFw1j/mPF753IRqTxb3RSCK5tuo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1286817142.12843.515.camel@xxxxxxxxxxxxxxxxxxxxxx>
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: <1286530426.12843.199.camel@xxxxxxxxxxxxxxxxxxxxxx> <1286817142.12843.515.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Oct 11, 2010 at 10:12 AM, Gianni Tedesco
<gianni.tedesco@xxxxxxxxxx> wrote:
> On Fri, 2010-10-08 at 10:33 +0100, Gianni Tedesco wrote:
>> Hi,
>>
>> I've been trying to boot stefano's minimal dom0 kernel from
>> git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git
>> 2.6.36-rc1-initial-domain-v2+pat
>>
>> On xen-unstable, I get the following WARN_ON()'s from Xen when bringing
>> up the NIC's, then the machine hangs forever when trying to login either
>> over serial or NIC.
>>
>> (XEN) Xen WARN at msi.c:649

I get the same Xen WARN messages using the current pvops/xen-next with
xen-unstable, here's the complete list for one boot, grep'd for WARN:

(XEN) Xen WARN at msi.c:636
(XEN) Xen WARN at msi.c:649
(XEN) Xen WARN at msi.c:636
(XEN) Xen WARN at msi.c:649
(XEN) Xen WARN at msi.c:656
(XEN) Xen WARN at msi.c:636
(XEN) Xen WARN at msi.c:649
(XEN) Xen WARN at msi.c:636
(XEN) Xen WARN at msi.c:649
(XEN) Xen WARN at msi.c:656
(XEN) Xen WARN at msi.c:636
(XEN) Xen WARN at msi.c:649
(XEN) Xen WARN at msi.c:656
(XEN) Xen WARN at msi.c:636
(XEN) Xen WARN at msi.c:649
(XEN)    0000000080287db8 0(XEN) Xen WARN at msi.c:636
(XEN) Xen WARN at msi.c:649
(XEN) Xen WARN at msi.c:656

The complete boot seq is attached.

I do get a login at the end of the boot seq though.
My situation goes pear shaped when I try start a pv domU. The dom0
locks up after printing this on the console:

(XEN) tmem: all pools frozen for all domains
(XEN) tmem: all pools thawed for all domains
(XEN) tmem: all pools frozen for all domains
(XEN) tmem: all pools thawed for all domains
mapping kernel into physical memory
about to get started...

then prints these once a minute:
[  589.490894] BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0]

The xen console is still active and I can generate a diag dump, also attached.

This dom0 lockup behavior started with pv-ops 2.6.32.21, all the way
to .24, rendering the later pvops kernels unusable for dom0.
The 2.6.32.18 kernel is the last one that functioned as a dom0.

This behavior is consistent on platforms, HP proliant 380DL G6, and
G7, as well as i7 supermicros.

-Bruce

>
> Hmm so this appears not to be an issue with XCP kernel, in that case I
> get the warnings but everything still works fine.
>
> I will investigate further when I have some time.
>
> Gianni
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

Attachment: dom0-2.6.32.24-boot.txt
Description: Text document

Attachment: dom0-2.6.32.24-xen-dump.txt
Description: Text document

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