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] network hang again

To: Brian Wolfe <ahzz@xxxxxxxxxxx>
Subject: Re: [Xen-devel] network hang again
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 15 Sep 2004 19:04:13 +0100
Cc: James Harper <JamesH@xxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 15 Sep 2004 19:22:05 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Wed, 15 Sep 2004 12:43:13 CDT." <1095270119.14282.6.camel@xxxxxxxxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> I do NOT get any errors from domain0, so I can't trace through to dom0
> right now. 8-(
> 
> This error coincides perfectly time wise with the linux-iscsi initiator
> errors I got earlier this week, so I believe that this is what's
> triggering the iscsi-initiator error.
> 
> Any advice on how to figure out what is causing the I/O error would be
> greatly appreciated. Right now it is the ONLY thing that is holding me
> back from using the IET iSCSI target.

You'll have to add tracing within generic_file_{read,write}. Those are
the interface into the buffer cache (pretty much) and below that you
enter the generic blkdev layer. Unfortunately the layers are pretty
thick, but hopefully you can drill back down the error paths fairly
quickly. 

Perhaps this might be related to the networking weirdnesses that
people are seeing? I can't explain the weird DOM0<->DOM1 ping
behaviour. 

 -- Keir


-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>