From owner-freebsd-questions Fri Jan 23 00:45:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13267 for questions-outgoing; Fri, 23 Jan 1998 00:45:43 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13257 for ; Fri, 23 Jan 1998 00:45:39 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id TAA13016; Fri, 23 Jan 1998 19:15:29 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id TAA19496; Fri, 23 Jan 1998 19:15:28 +1030 (CST) (envelope-from grog) Message-ID: <19980123191528.22710@lemis.com> Date: Fri, 23 Jan 1998 19:15:28 +1030 From: Greg Lehey To: Pirat Sriyotha Cc: questions@FreeBSD.ORG Subject: Re: [Q] device timeout References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: ; from Pirat Sriyotha on Fri, Jan 23, 1998 at 03:41:00PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk On Fri, Jan 23, 1998 at 03:41:00PM -0700, Pirat Sriyotha wrote: > hi, > > i am using FreeBSD 2.2.5-RELEASE #0 now. > it works quite well. But just one thing a moment ago > i've got a message that says that /kernel: ed0: device timeout. > > as i know, this means that i set irq to the wrong number, but i put the > right one to ed0. both port and irq are correct. > > please, so what does this mean for. The term "device timeout" isn't overly specific. It's from a driver that has expected an interrupt, and for some reason it didn't get it. There could be lots of reasons: - Could be that the board is set up incorrectly, as you suggest. This is one of the most common reasons. - Could be that the board is defective. - Could be that something else is missing. In the case of an Ethernet board, I'd guess that you have cabling problems. If that's not the case, and the board can support more than one kind of cable, check that it's set up for the correct cable. "man ed" will tell you what ifconfig flags you need for your particular cable. Greg