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/
Home Products Support Community News


Re: [Xen-devel] Instability with Xen, interrupt routing frozen, HPET bro

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Instability with Xen, interrupt routing frozen, HPET broadcast
From: Andreas Kinzler <ml-xen-devel@xxxxxx>
Date: Thu, 30 Sep 2010 12:16:55 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, JBeulich@xxxxxxxxxx
Delivery-date: Thu, 30 Sep 2010 03:17:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CA39898.8080304@xxxxxxxx>
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: <4C88A6F3.9020207@xxxxxx> <20100921115604.GP2804@xxxxxxxxxxx> <4CA38093.9070802@xxxxxx> <4CA39898.8080304@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100915 Thunderbird/3.1.4
On 29.09.2010 21:50, Jeremy Fitzhardinge wrote:
It is a Supermicro X8SIL-F, Intel Xeon 3450 system.
The big problem I had initially was instability with the integrated
ethernet until I disabled PCIe ASPM.  The symptom was that the ethernet
devices would disappear (ie, their PCI config space would start to read
all 0xff...)

I know that this is a known problem of Intel 82574L chips (on X8SIL) - it is discussed on "Intel Wired Ethernet" (http://sourceforge.net/projects/e1000/). That is why I tested different NICs (Intel ET Server Adapter (82576 [igb]) and Realtek 8168) and the problem remained. So I can say with certainty that the NIC and/or its power management is not the problem.

I also spend extensive time changing hardware components. I used a different mainboard (ASUS P7F-M), a different power supply, changed CPU, changed NICs (see above) - problems remained.

> That's exactly what my main test/devel machine is.  It has been very
> stable for me with xen-unstable.

We have a second Supermicro X8SIL-F, Intel Xeon 3450 system which only runs Linux PVM domains and it is totally stable (without my HPET patch). So I think as with all timing/race/deadlock/... issues it depends on what you do on your system. Let me give you my crash "recipe" [quite reliable ;-)]

Have two HVMs (called win1, win2) with Windows 7 x64 installed (do install everything twice, never clone, VM config attached). Install GPLPV, iometer 2006.07.27, prime95 25.11 x64. On both systems: start prime95 torture test (in-place large FFT) and using Windows task manager set CPU affinity on win1 of process prime95 to use only CPU1. On win2 do the same thing but to use only CPU0. Then start iometer on both VMs using the following parameters: have a second virtual disk in both VMs (so every windows has 2 virtual disks, one for Windows and one for iometer), use "# of outstanding I/Os" = 4, access spec = "All in one". Wait some minutes. Crash!

Regards Andreas

Attachment: win1.hvm
Description: Text document

Xen-devel mailing list