NetBSD Problem Report #9029
Received: (qmail 25010 invoked from network); 19 Dec 1999 19:14:00 -0000
Message-Id: <199912191913.MAA03301@amiga2.msu.montana.edu>
Date: Sun, 19 Dec 1999 12:13:57 -0700 (MST)
From: mhitch@montana.edu
Reply-To: mhitch@montana.edu
To: gnats-bugs@gnats.netbsd.org
Subject: elinkxl [ex] Ethernet driver appears to fail to acknowledge an interrupt
X-Send-Pr-Version: 3.95
>Number: 9029
>Category: kern
>Synopsis: The elinkxl driver appears to not acknowedge an interrupt at times.
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: mycroft
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Dec 19 11:15:00 +0000 1999
>Closed-Date: Mon Jul 26 04:06:43 +0000 2004
>Last-Modified: Mon Jul 26 04:06:43 +0000 2004
>Originator: Michael L. Hitch
>Release: 19991204
>Organization:
Montana State University
>Environment:
System: NetBSD alpha.msu.montana.edu 1.4P NetBSD 1.4P (PC164) #991204-7: Sat Dec 18 10:47:03 MST 1999 mhitch@alpha.msu.montana.edu:/usr/cvsroot/src/sys/arch/alpha/compile/PC164 alpha
>Description:
On my PC164, the 3Com 3c905B and 3c980 Ethernet cards would stop working after
relatively heavy network traffic. This would usually happen when I was
running xscreensaver on the PC164 and displaying on my Amiga. After finally
noticing a "stray interrupt" log message, I found that the alpha interrupt
handler was disabling the interrupt when no driver handled that interrupt.
Further investigation showed that the Ethernet cards appeared to be
generating an interrupt, and only the S_INTR_LATCH was set in the status
register (which was not considered an interrupt condition).
>How-To-Repeat:
Install a 3Com 3c980 or 3c905B Ethernet card in an Alpha PC164, run lots
of network traffic over that adapter for a while, and wait for the driver
to stop functioning because the interrupt gets disabled.
>Fix:
Possibly include the S_INTR_LATCH in interrupt status bits, since that
status bit appears to be abled to be cleared by the software.
The following patch separately checks for the S_INTR_LATCH status bit being
set when no other interrupt status was present, displays a console message,
clears the S_INTR_LATCH status, and indicates the driver handled the interrupt.
The interfaces now periodically report this message, and continue to function.
--- elinkxl.c.orig Sun Dec 19 11:51:06 1999
+++ elinkxl.c Sun Dec 19 12:09:38 1999
@@ -1109,8 +1116,15 @@
}
for (;;) {
stat = bus_space_read_2(iot, ioh, ELINK_STATUS);
- if (!(stat & S_MASK))
+ if (!(stat & S_MASK)) {
+ if (ret == 0 && (stat & S_INTR_LATCH) != 0) {
+ printf("%s: %x intr_latch set, clearing\n",
+ sc->sc_dev.dv_xname, stat);
+ bus_space_write_2(iot, ioh, ELINK_COMMAND, C_INTR_LATCH);
+ ret = 1;
+ }
break;
+ }
/*
* Acknowledge interrupts.
*/
>Release-Note:
>Audit-Trail:
From: Matthias Drochner <M.Drochner@fz-juelich.de>
To: mhitch@montana.edu
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/9029: elinkxl [ex] Ethernet driver appears to fail to
acknowledge an interrupt
Date: Mon, 20 Dec 1999 19:00:21 +0100
How is this related to the patch I sent to a mailing list
a while ago? Did that work? Pros/cons of the versions?
best regards
Matthias
From: "Michael L. Hitch" <mhitch@msu.oscs.montana.edu>
To: M.Drochner@fz-juelich.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/9029: elinkxl [ex] Ethernet driver appears to fail to
acknowledge an interrupt
Date: Mon, 20 Dec 1999 14:47:31 -0700
Matthias Drochner <M.Drochner@fz-juelich.de> writes:
> How is this related to the patch I sent to a mailing list
> a while ago? Did that work? Pros/cons of the versions?
It should be equivalent to your patch, but does not got through the
checks to see what the interrupt was, and it also displays a message
when it gets only the S_INTR_LATCH status set [I wanted to know when
this condition occured, and how often].
I didn't try your patch yet; I was trying to get the interfaces to
fail again after my hack re-enabled the interrupts when the interface
timed out, and wanted to test my patch before I left on vacation. I
won't be able to test your patch out util January.
Michael
---
Michael L. Hitch mhitch@montana.edu
Computer Consultant, Information Technology Center
Montana State University, Bozeman, MT USA
From: Andrew Brown <atatat@atatdot.net>
To: Matthias Drochner <M.Drochner@fz-juelich.de>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/9029: elinkxl [ex] Ethernet driver appears to fail to acknowledge an interrupt
Date: Wed, 18 Jul 2001 22:20:03 -0400
any chance of getting either of these patches integrated? my alpha
falls over somewhat regularly because of this, and due to the fact
that my console no longer works (long story, ask me if you care), i am
forced to power cycle the machine rather violently instead of dropping
into ddb and merely re-enabling the interrupt.
--
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org * "ah! i see you have the internet
twofsonet@graffiti.com (Andrew Brown) that goes *ping*!"
andrew@crossbar.com * "information is power -- share the wealth."
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: mhitch@montana.edu
Cc: gnats-bugs@gnats.netbsd.org, M.Drochner@fz-juelich.de
Subject: Re: kern/9029: elinkxl [ex] Ethernet driver appears to fail to acknowledge an interrupt
Date: Fri, 2 Aug 2002 15:32:00 +0200
Hi,
do you know if this is still a problem with 3c9xx on alphas ?
http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=9029
--
Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr
--
From: "Michael L. Hitch" <mhitch@msu.oscs.montana.edu>
To: bouyer@antioche.lip6.fr
Cc: gnats-bugs@gnats.netbsd.org, M.Drochner@fz-juelich.de
Subject: Re: kern/9029: elinkxl [ex] Ethernet driver appears to fail to
acknowledge an interrupt
Date: Mon, 5 Aug 2002 16:15:41 -0600
Manuel Bouyer <bouyer@antioche.lip6.fr> writes:
> Hi,
> do you know if this is still a problem with 3c9xx on alphas ?
>
> http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=9029
I am not real certain at the moment. There have been changes to the
driver which may have fixed this. I have one system with dual 3c9xxx
interfaces running 1.6_BETA4 that have not experienced the problem, but
this system was a realtively recent aquisition and may not be experiencing
the conditions that exhibited this problem. My PC164 (which is the
system I had problems on) is still running 1.5.3_ALPHA. I've been
trying to get a change to upgrade it to 1.6_BETA*, at which point I
should be able to test this under the same conditions as when the
problem previously occurred.
I was looking at the driver code and had originally thought it might
still have the problem, but after Charles beat me on the head a couple
of times, I came to the conclusion that the driver looks like it *should*
be doing the right thing now. But until I actually run it, I can't say
for sure the problem is gone.
Michael
---
Michael L. Hitch mhitch@montana.edu
Operations Consulting, Information Technology Center
Montana State University, Bozeman, MT USA
State-Changed-From-To: open->feedback
State-Changed-By: mycroft
State-Changed-When: Tue Jul 6 22:11:08 UTC 2004
State-Changed-Why:
No feedback in two years. What's the deal?
Responsible-Changed-From-To: kern-bug-people->mycroft
Responsible-Changed-By: mycroft
Responsible-Changed-When: Tue Jul 6 22:11:08 UTC 2004
Responsible-Changed-Why:
.
From: "Michael L. Hitch" <mhitch@msu.oscs.montana.edu>
To: gnats-bugs@gnats.netbsd.org
Cc:
Subject: Re: kern/9029
Date: Fri, 23 Jul 2004 15:50:29 -0600
> State-Changed-From-To: open->feedback
> State-Changed-By: mycroft
> State-Changed-When: Tue Jul 6 22:11:08 UTC 2004
> State-Changed-Why:
> No feedback in two years. What's the deal?
I believe the last time I looked at this, the driver interrupt
code had been changed slightly and no longer exhibited this problem.
My PC164 is *still* running 1.5.3_ALPHA, so I haven't been able to
update to a newer version of the driver to verify the original problem.
Another machine (an AlphaServer 800) has been running 1.6.1 without
modifications to elinkxl.c for 9 months now, and has had very large
amounts of traffic on both 3c905C-TX NICs with no problems. I can't
remember now if these ever had the same problem, and probably had
modified elinkxl.c when I was running earlier versions of NetBSD,
so I can't say for sure that machine ever had the same problem. In
addition, the NIC in my PC164 is a 3c980, so the NIC is different.
I do have another machine with a 3c980 NIC, which I just upgraded to 2.0G.
Again, I can't remember if I had seen the same problem on this machine.
So in summary - I think the problem no longer exists, but am not able
to currently verify it.
---
Michael L. Hitch mhitch@montana.edu
Operations Consulting, Information Technology Center
Montana State University, Bozeman, MT USA
State-Changed-From-To: feedback->closed
State-Changed-By: mycroft
State-Changed-When: Mon Jul 26 04:06:14 UTC 2004
State-Changed-Why:
Problem does not appear to exist any more. Will let someone else open a new
PR if necessary.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.