From owner-freebsd-questions Mon Nov 11 14:24:55 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15568 for questions-outgoing; Mon, 11 Nov 1996 14:24:55 -0800 (PST) Received: from battra.telebase.com (root@battra.telebase.com [192.132.57.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA15537 for ; Mon, 11 Nov 1996 14:24:36 -0800 (PST) Received: from wormhole.telebase.com by battra.telebase.com id RAA19988 for ; Mon, 11 Nov 1996 17:24:22 -0500 (EST) Received: from odo.telebase.com (odo.telebase.com [172.16.2.217]) by wormhole.telebase.com (8.8.2/8.8.1) with ESMTP id RAA04471 for ; Mon, 11 Nov 1996 17:24:21 -0500 (EST) Received: (from bmc@localhost) by odo.telebase.com (8.8.1/8.8.1) id RAA00689; Mon, 11 Nov 1996 17:24:21 -0500 (EST) Date: Mon, 11 Nov 1996 17:24:21 -0500 (EST) Message-Id: <199611112224.RAA00689@odo.telebase.com> From: Brian Clapper To: questions@freebsd.org Subject: Re: ed0 device timeout In-Reply-To: <129302942@toto.iv> Organization: N2K Inc Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > We had the same problem with ed0 'Device timeout'. In our > case it was because the ethernet card was set to a > different IRQ than the FreeBSD IRQ. > Also, it could be due to an IRQ conflict, eg a SoundBlaster > trying to use the same interrupt. Also, at the risk of stating the extremely obvious, be sure to check *all* hardware. I had the same problem over the weekend with an old 10Base2 (cheapernet) card. I checked and rechecked all IRQs and even swapped cards, with no luck. The terminators turned out to be faulty. As soon as I put on two brand new terminators, the timeouts stopped, and the network started working. ---- Brian Clapper ................................................... bmc@n2k.com http://www.netaxs.com/~bmc/ ............. PGP public key available on request Failing to get them to do it your way might mean they're stupid, but it also means you failed to get them to do it your way. -- Cal Keegan