From owner-freebsd-hackers  Mon Jun  5 04:10:46 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id EAA19246
          for hackers-outgoing; Mon, 5 Jun 1995 04:10:46 -0700
Received: from pyromania.apana.org.au (pyromania.apana.org.au [202.12.87.123])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA19233
          for <hackers@freebsd.org>; Mon, 5 Jun 1995 04:10:35 -0700
Received: (from john@localhost) by pyromania.apana.org.au (8.6.9/8.6.9) id VAA01221 for hackers@freebsd.org; Mon, 5 Jun 1995 21:10:09 +1000
From: John Herks <john@pyromania.apana.org.au>
Message-Id: <199506051110.VAA01221@pyromania.apana.org.au>
Subject: ed0 - device timeout ?
To: hackers@freebsd.org
Date: Mon, 5 Jun 1995 21:10:09 +1000 (EST)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 513       
Sender: hackers-owner@freebsd.org
Precedence: bulk

I am randomly getting ed0 kernel device timeout messages from my Freebsd 
2.0R machine...

I am running a NE2000 clone network card...

(I have other devices on the network running OK - and the cabling is fine.)

Is the card faulty or should I be using a different NIC with better 
driver code in the Kernel ?

Here is my dmesg output:
ed0 at 0x280-0x29f irq 5 on isa
ed0: address 00:00:01:04:80:53, type NE2000 (16 bit) 

Errors-:
ed0: device timeout
ed0: device timeout

John Herks
john@pyromania.apana.org.au