Article View: comp.sys.next.hardware
Article #93Re: spurious DMA interrupt: channel 0x2000110
From: Jeff Hallgren
Date: Fri, 30 Oct 1992 13:02
Date: Fri, 30 Oct 1992 13:02
20 lines
1227 bytes
1227 bytes
In article <1992Oct29.160928.12647@stc.nato.int> koelman@cuby.stc.nl (Ton Koelman) writes: > > spurious DMA interrupt: channel 0x2000110 > > Does anyone ever get this? > It seems to coincide with heavy ethernet traffic... I get the same message. It shows up after about an hour after I power on and seems pretty harmless so far. I'd also like to find out whether it indicates problems or not. PS: 8MB/250MB 25Mhz 040 slab, running 3.0 (swap city) w/ CD drive, and NO ethernet, using SLIP instead. Jeff Jeff Hallgren/Convergent Medical Systems Lab Information Services/University of Minnesota Hospital and Clinic Email: jhall@tahiti.umhc.umn.edu
Technical Details
Message-ID:
<1992Oct30.130230.15104@news2.cis.umn.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!wupost!darwin.sura.net!spool.mu.edu!umn.edu!newsReferences:
<1992Oct29.160928.12647@stc.nato.int>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.hardware Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!darwin.sura.net!spool.mu.edu!umn.edu!news From: jhall@tahiti.umhc.umn.edu (Jeff Hallgren) Subject: Re: spurious DMA interrupt: channel 0x2000110 Message-ID: <1992Oct30.130230.15104@news2.cis.umn.edu> Sender: news@news2.cis.umn.edu (Usenet News Administration) Nntp-Posting-Host: barbados.umhc.umn.edu Reply-To: jhall@tahiti.umhc.umn.edu Organization: University of Minnesota References: <1992Oct29.160928.12647@stc.nato.int> Date: Fri, 30 Oct 1992 13:02:30 GMT Lines: 20