Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!ginosko!uunet!mcvax!unido!fauern!immd4.informatik.uni-erlangen.de!mlelstv
From: mlelstv@immd4.informatik.uni-erlangen.de (Michael van Elst )
Newsgroups: comp.sys.amiga
Subject: Re: Guru explanation needed
Message-ID: <493@medusa.informatik.uni-erlangen.de>
Date: 22 Aug 89 14:14:07 GMT
References: <3142@bucsb.UUCP>
Organization: IMMD IV, University of Erlangen, W-Germany
Lines: 27

bear@bucsb.UUCP (Blair M. Burtan) writes:

>I need some guru number explanations.

>Here's the scenario:  I'm playing w/ my 2 meg A1000 shuffling
>           one and double-click it.  POOF.  The power light
>           flashes.  I reset the machine and I get a guru
>           number like 00000004.002292A0 or 9030 or 9250.

>But what I want to know is why the system crashes in the first
>place and why I get a guru AFTER a reset.

Don't know why the Amiga crashes when swapping disks. There
was mentioned a problem with bad allocation bitmaps that are
marked as valid resulting in "disk corrupt..." requesters.
Another problem might be a corrupted disk.info file. Workbench
isn't very smart in handling these.

The guru AFTER the reset is just ok. If the system can't
show you the alert because of corrupted gfx,intuition or exec
data structures, i.e. exec is trapped during the Alert() routine,
the system reboots and the alert.hook module shows you the last
alert that was initiated. Then it continues with the bootstrap.

				Michael van Elst

E-mail: UUCP: ...uunet!unido!fauern!immd4!mlelstv