home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.m68k
- Path: sparky!uunet!paladin.american.edu!europa.asd.contel.com!darwin.sura.net!wupost!gumby!destroyer!ubc-cs!unixg.ubc.ca!kakwa.ucs.ualberta.ca!acs.ucalgary.ca!norm
- From: norm@enel.ucalgary.ca (Norm Bartley)
- Subject: Re: problems with m68882
- Sender: news@acs.ucalgary.ca (USENET News System)
- Message-ID: <92Sep08.184615.11893@acs.ucalgary.ca>
- Date: Tue, 08 Sep 92 18:46:15 GMT
- References: <219@F_HOME.ahwau.ahold.nl>
- Nntp-Posting-Host: eneli.enel.ucalgary.ca
- Organization: ECE Department, U. of Calgary, Calgary, Alberta, Canada
- Keywords: m68882
- Lines: 20
-
- In article <219@F_HOME.ahwau.ahold.nl> leo@ontnix2.ahwau.ahold.nl (Leo Weppelman) writes:
- >I am working on an multi-tasking kernel on my Atari-TT. It contains an
- >68030 main processor and an 68882 coprocessor on 33Mhz.
- >
- >I am getting coprocessor protocol violations at random but especially
- >when a lot of interrupts occur (i.e. during disk accesses).
-
- I have had similar problems on my Amiga while trying to add 68882
- support to Amiga Minix. I followed the exact same procedure as you for
- saving/restoring/initializing the 68882 context. I would get coprocessor
- protocol violations at random -- a process might bomb immediately, or it
- might run for a few seconds and then bomb.
-
- I was never been able to resolve this problem. I, too, suspected
- interrupts from various things, but I added code to the kernel to
- catalogue and report all interrupts -- nothing had anything to do
- with the 68882.
-
- Best wishes,
- Norm Bartley, norm@enel.ucalgary.ca
-