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] Xen-Unstable : no eth0 when boot up

To: "Yan Li" <yan_li00@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen-Unstable : no eth0 when boot up
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 02 Jul 2004 08:46:34 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 02 Jul 2004 08:47:51 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Fri, 02 Jul 2004 00:16:30 PDT." <BAY16-DAV10tn1t8LNC00026326@xxxxxxxxxxx>
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
> unfortunaly new problems comes. :(
> I noticed long ago that after install xen, 'halt' didn't work, it just acted
> like reboot. So I wanna try it on this 1.3, and it turned that it still just
> reboots the machine. And I trid this on two xen machines, both worked this
> way.

'halt' doesn't seem very useful, but it's easily implemented.

> More serious problems is after this reboot, eth0 lost again. I didn't change
> anything since eth0 was up. I'm sure the .config has set e100=y. So I 'make
> clean' and 'make world' 'make install' again, still didn't work.
> e100:selftest timeout
> e100:failed to initialize, instance #0
> hello world from e100_init_module

Sounds like the selftest is marginal. Can you increase the timeout in
e100_selftest, or check the return value from schedule_timeout (it
maybe returnign early), or perhaps try calling e100_selftest a few
time before failing?

 -- Keir

This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
Xen-devel mailing list