From owner-freebsd-hackers  Mon Jun  5 07:35:54 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id HAA03846
          for hackers-outgoing; Mon, 5 Jun 1995 07:35:54 -0700
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA03795
          for <hackers@freebsd.org>; Mon, 5 Jun 1995 07:35:38 -0700
Received: (from imb@localhost)
	by asstdc.scgt.oz.au (8.6.12/BSD4.4)
	id AAA17055; Tue, 6 Jun 1995 00:34:06 +1000
From: michael butler <imb@scgt.oz.au>
Message-Id: <199506051434.AAA17055@asstdc.scgt.oz.au>
Subject: Re: ed0 - device timeout ?
To: john@pyromania.apana.org.au (John Herks)
Date: Tue, 6 Jun 1995 00:34:05 +1000 (EST)
Cc: hackers@freebsd.org
In-Reply-To: <199506051110.VAA01221@pyromania.apana.org.au> from "John Herks" at Jun 5, 95 09:10:09 pm
X-Mailer: ELM [version 2.4 PL24beta]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 374       
Sender: hackers-owner@freebsd.org
Precedence: bulk

John Herks writes:

> I am randomly getting ed0 kernel device timeout messages from my Freebsd 
> 2.0R machine...
 
> I am running a NE2000 clone network card...
 
This usually only occurs because the interrupt level the kernel thinks the
card is using is not the same as that which the card is physically set up
for or that it is in conflict with something else,

	michael