Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!news.kei.com!news.mathworks.com!howland.erols.net!netcom.com!kashani
From: kashani@netcom.com (Ken Kashani)
Subject: Re: Device timeout (2.1.5 + Intel ether16)
Message-ID: <kashaniE1yI21.DqK@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
X-Newsreader: TIN [version 1.2 PL1]
References: <kashaniE1yEM4.Mvx@netcom.com>
Date: Thu, 5 Dec 1996 19:56:25 GMT
Lines: 61
Sender: kashani@netcom.netcom.com
I also wanted to add one more thing. I _did_ find the following
in the FAQ:
2.18. I keep seeing messages like ``ed1: timeout''.
This is usually caused by an interrupt conflict (e.g., two boards using
the same IRQ). FreeBSD prior to 2.0.5R used to be
tolerant of this, and the network driver would still function in the
presence of IRQ conflicts. However, with 2.0.5R and later,
IRQ conflicts are no longer tolerated. Boot with the -c option and change
the ed0/de0/... entry to match your board.
The intr. on the card is 10. I booted with the -c option and found
a couple CDROM drivers set as 10 and removed them. But I'm still
getting the same message. May be I'll just go ahead and change the int
on the Intel card. (If you can't solve it, avoid it :-)
-Ken
Ken Kashani (kashani@netcom.com) wrote:
: We have recently installed FreeBSD 2.1.5 on a Pentium 133
: system to use as a web server. The server has an Intel
: Etherexpress 16 card in it.
: All seemed fine until we started to test Apache by viewing
: web pages on that system. On occasion the system would seem
: to stop serving pages (for a fraction of a second) and then
: printout the following message:
: /kernel: ix0: device timeout
: Although the system is new I have to admit that the Intel card
: is from an older system. The card worked fine in the previous
: system (not running freeBSD).
: Has anyone experienced this?
: Is there a Kernel configuration for resolving this or should the
: card be changed (mabe upgraded to a newer card or another card
: totally)?
: Any words of wisdom are welcomed.
: Thanks.
: -Ken
: --
: kashani@netcom.com
--
kashani@netcom.com