Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!bryce
From: bryce@cbmvax.commodore.com (Bryce Nesbitt)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Scheduler changed under 2.0?
Message-ID: <15847@cbmvax.commodore.com>
Date: 14 Nov 90 07:27:26 GMT
References: <90312.082534GIAMPAL@auvm.auvm.edu>
Reply-To: bryce@cbmvax.commodore.com (Bryce Nesbitt)
Organization: Commodore, West Chester, PA
Lines: 24

In article <90312.082534GIAMPAL@auvm.auvm.edu> GIAMPAL@auvm.auvm.edu writes:
>I've got a semi-simple question about the Scheduler and LoadSeg() under 2.0...
>
>For example, on an A3000, if you start a ray-
>trace with TurboSilver and pop back to workbench to start up something like
>DeluxePaint, the entire system _seems_ locked, but then suddenly jumps back
>to life in little bursts. 

On the A3000 attempts to access illegal memory results in a "Bus Error".
(For anything not otherwise filled, the A3000 Hardware asserts _BERR).
Each illegal memory access takes 250 milliseconds.  Programs like the ones
you mention sometimes read/write/trash random areas of memory.

Under 1.3 emulation on the A3000, the address space is mapped differently,
hiding the feature.

The only way to tell for sure would be to get the developer tool called
"Enforcer", and check if the pauses are coincident with illegal memory hits.

-- 
|\_/|  . "ACK!, NAK!, EOT!, SOH!"  "Lawyers: America's untapped export market."
{X o} .     Bryce Nesbitt, Operating Systems Group, Commodore-Amiga, Inc.
 (")        BIX: bnesbitt
  U	    USENET: bryce@commodore.COM -or- uunet!cbmvax!bryce