home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!munnari.oz.au!uniwa!cujo!marsh!cproto
- From: cproto@marsh.cs.curtin.edu.au (Computer Protocol)
- Subject: Re: Some more on NMI problems (some meager advancement)
- Message-ID: <cproto.715945053@marsh>
- Sender: news@cujo.curtin.edu.au (News Manager)
- Organization: Curtin University of Technology
- References: <1992Sep7.014351.946@ponds.uucp>
- Date: Tue, 8 Sep 1992 09:37:33 GMT
- Lines: 30
-
- rivers@ponds.uucp (Thomas David Rivers) writes:
-
-
- >Well, I thought I would relay my current status with the NMI
- >investigation.
-
- > Right now, I'm thinking it has something to do with an IDE
- > controller/disk drive, so I have been examining the wd.c driver
- > trying to divine what it might be; without too much luck. (I
- > know very little about the IDE/WD disk controllers.)
-
- [STUFF DELETED]
-
- > - Dave Rivers -
- > (rivers@ponds.uucp)
-
- I'm also experiencing the problem. I disagree with the IDE controller
- idea. I still think it's a spurious parity error. Note that the NMI
- interrupt reports the value of I/O port 61. This value has the highest
- bit set which indicates a parity error. But after running QAPLUS for
- several days I'm convinced my memory is ok.
-
- Could it be some sort of setup problem - e.g. wait states which can
- be configured in my AMI BIOS.
-
- BTW I do have a IDE controller/disk so Dave might be right.
-
- Regards - Tibor Sashegyi (cproto@abel.cs.curtin.edu.au)
-
-
-