From owner-freebsd-hackers  Thu May 29 17:14:00 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id RAA17247
          for hackers-outgoing; Thu, 29 May 1997 17:14:00 -0700 (PDT)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA17242
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 29 May 1997 17:13:57 -0700 (PDT)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id RAA01679;
	Thu, 29 May 1997 17:09:48 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd001676; Fri May 30 00:09:42 1997
Message-ID: <338E1A9C.41C67EA6@whistle.com>
Date: Thu, 29 May 1997 17:09:00 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: pvl@nanoteq.com
CC: FreeBSD-hackers <freebsd-hackers@FreeBSD.ORG>
Subject: Re: ed0 : device timeout
References: <199705291506.RAA01207@oskar.nanoteq.co.za>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Pierre Van Leeuwen wrote:
> 
> Hi
> 
> I wrote to questions about this earlier, but that didn't solve my
> problem.
> 
> I get the following message :
> ed0 : device timeout
> 
> It doesn't seem to be fatal all the time though.
> 
> Looking at if_ed.c I see it is because the device doesn't
> generate an interrupt after a transmit was started.
> I commented the line out that checks for the interrupt,
> and had the function return without doing anything. Didn't
> do any good as expected.
> 
> It's a D-Link De-220 card which I have exchanged about three
> times, as well as putting a new motherboard in. The
> only thing I haven't changed is the cpu (Pentium 133).
> I've been running FreeBSD on it since 2.1.5 and I have
> 2.2-Stable on it at the moment (CVSupped about a week ago --
> I tried to CVSup today, but today the ed0 error is fatal :)  )

use the correct interrupt?

the ethernet will still work slowely with the wrong interrupt
except for the messages..