Article View: comp.sys.next.misc
Article #3531Re: Spurious DMA interrupt messages on '040 Cube
From: Louis A. Mamakos
Date: Tue, 29 Sep 1992 12:46
Date: Tue, 29 Sep 1992 12:46
23 lines
1541 bytes
1541 bytes
In article <12539@optilink.UUCP> brad@optilink.UUCP (Brad Yearwood) writes: >Does anyone recognize the following console messages as being indicative >of something going bad in the Ethernet interface of an '040 Cube? > > en0: transmitter not ready > spurious DMA interrupt > Spurious DMA interrupt - state = 1000000 @ 2000110 > Spurious DMA interrupt - state = 1000000 @ 2000110 > spurious DMA interrupt > The network is disabled or your computer isn't connected to it. We had similar problems with a couple of Cubes (running Release 2.1) on a network. In that case, the problem was worse; the machines would frequently panic. It turned out that we had a bad repeater, and an excessively high number of collisions on that ethernet segment. Once we replaced the repeater, stuff returned to normal. Now, it seems somewhat rude for the NeXTs on that segment to panic and die to due excessive collisions. Especially considering the 4 DECstation 5000 systems and a few other random boxes didn't do anything untoward at the time... louie
Technical Details
Message-ID:
<1992Sep29.124618.26760@ni.umd.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!ni.umd.edu!sayshell.umd.edu!louieReferences:
<12539@optilink.UUCP>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.misc Path: arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!ni.umd.edu!sayshell.umd.edu!louie From: louie@sayshell.umd.edu (Louis A. Mamakos) Subject: Re: Spurious DMA interrupt messages on '040 Cube Message-ID: <1992Sep29.124618.26760@ni.umd.edu> Sender: usenet@ni.umd.edu (USENET News System) Nntp-Posting-Host: sayshell.umd.edu Organization: University of Maryland, College Park References: <12539@optilink.UUCP> Date: Tue, 29 Sep 1992 12:46:18 GMT Lines: 23