Re: [Xen-devel] MSI badness in xen-unstable

[Bruce Edge <bruce.edge@xxxxxxxxx>]

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