From owner-freebsd-hackers Thu Jun 27 18:26:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18625 for hackers-outgoing; Thu, 27 Jun 1996 18:26:58 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA18618 for ; Thu, 27 Jun 1996 18:26:55 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA14345; Fri, 28 Jun 1996 10:44:23 +0930 From: Michael Smith Message-Id: <199606280114.KAA14345@genesis.atrad.adelaide.edu.au> Subject: Re: ed0 -- device timeout To: nick_liu@hud.gov (nick liu) Date: Fri, 28 Jun 1996 10:44:23 +0930 (CST) Cc: hackers@freebsd.org In-Reply-To: <9606280044.AA00882@hud.gov> from "nick liu" at Jun 27, 96 05:53:28 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk nick liu stands accused of saying: > > > I am randomly getting ed0 kernel device timeout messages from my Freebsd > > 2.0R machine... This is almost certainly in the FAQ or the handbook. What it means is that the driver isn't getting interrupts from the card. One of the following is true : - You have a cabling problem. - You have selected the wrong media type on the card. - You have an IRQ configuration error (this may include PCI BIOS config). - Your card is stuffed. > > Is the card faulty or should I be using a different NIC with better > > driver code in the Kernel ? The 'ed' driver is rock-solid. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[