From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Kinzler <ml-xen-devel@hfp.de>
Subject: Re: RE: Stability report GPLPV 0.11.0.308
Date: Fri, 30 Sep 2011 11:17:25 +0200
Message-ID: <4E858925.6090903@hfp.de>
References: <4E64A0DF.2070007@hfp.de>
	<AEC6C66638C05B468B556EA548C1A77D01E5DB8C@trantor>
	<4E64D569.5030607@hfp.de>
	<AEC6C66638C05B468B556EA548C1A77D01E5DBBF@trantor>
	<4E7728F9.9020208@hfp.de>
	<AEC6C66638C05B468B556EA548C1A77D01E5E008@trantor>
	<4E7B04A4.9070601@hfp.de>
	<AEC6C66638C05B468B556EA548C1A77D01E5E072@trantor>
	<4E7CF2A8.5040405@hfp.de>
	<AEC6C66638C05B468B556EA548C1A77D01E5E0D0@trantor>
	<4E808FE9.5050008@hfp.de>
	<AEC6C66638C05B468B556EA548C1A77D01E5E190@trantor>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01E5E190@trantor>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Hello James,

> 12961573357740: *** Assertion failed: pi.curr_mdl
> 12961573357740: ***   Source File:
> c:\projects\win-pvdrivers.hg\xennet\xennet6_tx.c, line 308

I took this report about a problem you had with "tx" to modify my tests 
and to make them mostly tx-based while previously they were mostly 
rx-based. Tests are running for 2d 18h now - no problems so far.

I wanted to tell you about one interesting observation. In my tests I 
did two runs with modified xenvbd drivers. In run #1 I switched to the 
scsiport driver of 0.11.0.312 and this made one domU crash after one day 
while with 0.11.0.312 storport version I always had more than 9 days (as 
I reported earlier). In run #2 I forward-ported xenvbd from 0.11.0.213 
(which is totally stable on our systems) and again one domU crashed 
after one day. This is really interesting and leads me to two thoughts:

1) xennet has some problem, but still why does scsiport vs. storport 
make a difference then?
2) perhaps there is some new bug outside xennet and outside xenvbd (some 
infrastructure thing: event handling, PCI, ...) and this is the real reason.

> Can you have a look in your logs for anything like this? I'm curious as
> to if we are chasing the same problem or a different one.

I am not running kernel debugging so far (have played with it though). 
So I cannot say.

Regards Andreas