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: "Yan Li" <yan_li00@xxxxxxxxxxx>
Subject: Re: [Xen-devel] desperate for help on netwrok of xen
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Thu, 29 Jul 2004 11:52:27 +0100
Cc: "Steven Hand" <Steven.Hand@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 29 Jul 2004 11:52:27 +0100
Envelope-to: Steven.Hand@xxxxxxxxxxxx
In-reply-to: Your message of "Thu, 29 Jul 2004 03:33:00 PDT." <BAY16-DAV8t3V5g2oHz00037a3d@xxxxxxxxxxx>
> e100 works fine in regular linux, and actually I tried in another machine
> with e100, just the same problem.
> and the second machine with 2 NICs also works fine in regular machine, using
> eth1.
> And here's the msg from dmesg and XendDmesg.py. This is for the machine only
> with e100.


> 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? 


static unsigned char __devinit
e100_init(struct e100_private *bdp)
    u32 st_timeout = 0;
    u32 st_result = 0;

    if (!e100_selftest(bdp, &st_timeout, &st_result)) {
            if (st_timeout) {
            printk(KERN_ERR "e100: selftest timeout\n");
        } else {
            printk(KERN_ERR "e100: selftest failed. Results: %x\n",
#if 0
        return false;
        printk(KERN_DEBUG "e100: selftest OK.\n");

    /* read the MAC address from the eprom */


We can try to see if we can track it down over here (we have few 
e100 cards but should be able to manage).