From owner-freebsd-hackers  Sun Nov 16 11:16:43 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA07949
          for hackers-outgoing; Sun, 16 Nov 1997 11:16:43 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA07935
          for <freebsd-hackers@FreeBSD.ORG>; Sun, 16 Nov 1997 11:16:39 -0800 (PST)
          (envelope-from sjr@home.net)
Received: (from sjr@localhost)
	by istari.home.net (8.8.7/8.8.6) id OAA13572
	for freebsd-hackers@FreeBSD.ORG; Sun, 16 Nov 1997 14:16:37 -0500 (EST)
Date: Sun, 16 Nov 1997 14:16:37 -0500 (EST)
From: "Stephen J. Roznowski" <sjr@home.net>
Message-Id: <199711161916.OAA13572@istari.home.net>
To: freebsd-hackers@FreeBSD.ORG
Subject: Diagnosing Intel EtherExpress Pro/10+ problem
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I'm been having a reoccuring problem with an Intel EtherExpress Pro/10+
Ethernet card. When I reboot into FreeBSD from Windows 95, occasionally
the card won't come back in a working state. Rebooting multiple times
will cause the card to eventually work. [This is on an 18 October kernel,
but has occurred on earlier kernels as well.]

Each time, the card seems to be recognized correctly during the probe,
but when I try to (for example) ping a remote address, I get a "no route
to host" message [not sure of exact wording]. If I configure the interface
down, then back up, I get a "could not allocate llinfo" error.

My question is, how can I go about diagnosing (and fixing :-) this problem?

Thanks,
-SR