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] desperate for help on netwrok of xen

To: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] desperate for help on netwrok of xen
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Thu, 29 Jul 2004 11:56:21 +0100
Cc: "Yan Li" <yan_li00@xxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 29 Jul 2004 11:56:21 +0100
Envelope-to: Steven.Hand@xxxxxxxxxxxx
In-reply-to: Your message of "Thu, 29 Jul 2004 11:52:27 BST." <E1Bq8WR-00039s-00@xxxxxxxxxxxxxxxxx>
> [snip] 
> > e100: selftest timeout
> > e100: Failed to initialize, instance #0
> so this looks like the culprit; we have noticed something similar 
> with the 2.6 xenlinux code and not sure why it happens (only some
> times it appears). Anyway can you comment out line 1283 in 
> linux-2.4.26-xen0/drivers/net/e100/e100_main.c to ignore the failure 
> and see if it in fact just works? 

Or, better change the value of E100_MAX_SCB_WAIT in e100.h from 
100 to e.g. 5000.