All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kinzler <ml-xen-devel@hfp.de>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
Subject: Re: RE: Stability report GPLPV 0.11.0.308
Date: Fri, 30 Sep 2011 11:17:25 +0200	[thread overview]
Message-ID: <4E858925.6090903@hfp.de> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01E5E190@trantor>

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

  reply	other threads:[~2011-09-30  9:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-05 10:13 Stability report GPLPV 0.11.0.308 Andreas Kinzler
2011-09-05 10:31 ` James Harper
2011-09-05 13:58   ` Andreas Kinzler
2011-09-06  5:21     ` James Harper
2011-09-12 21:39       ` Andreas Kinzler
2011-09-19 11:35       ` Andreas Kinzler
2011-09-21 23:30         ` James Harper
2011-09-22  9:49           ` Andreas Kinzler
2011-09-22 10:10             ` James Harper
2011-09-23 20:57               ` Andreas Kinzler
2011-09-23 23:49                 ` James Harper
2011-09-26 14:44                   ` Andreas Kinzler
2011-09-27  0:59                     ` James Harper
2011-09-27  5:45                     ` James Harper
2011-09-30  9:17                       ` Andreas Kinzler [this message]
2011-09-30 10:06                         ` James Harper
2011-09-30 10:09                         ` James Harper
2011-10-01 11:10                           ` Andreas Kinzler
2011-10-10 16:07                             ` Andreas Kinzler
2011-09-30 10:17                         ` James Harper
     [not found]                         ` <AEC6C66638C05B468B556EA548C1A77D01E5E2E4@trantor>
2011-10-01  9:28                           ` Andreas Kinzler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E858925.6090903@hfp.de \
    --to=ml-xen-devel@hfp.de \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.