|Re: [hatari-devel] Latest Hatari crashing|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Latest Hatari crashing
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Sat, 15 Jun 2019 14:37:48 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1560602268; s=strato-dkim-0002; d=seimet.de; h=In-Reply-To:References:Message-ID:Subject:To:From:Date: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=C4Fc34r2B8cyIBIQ3pzQGVmBo2N7ELi5aDhaTILsZos=; b=i0sV1u3VESRHghBIDzummHwi+aprLBVEFcBII24BsqLscNuyTPtNYLZTjBuKCBzYDQ VhX1zaUv/AiYMXvv2N6n3OW0ak7kpXqSeOzqgtFQZC/lOZFkxVbde5YZDrWJIhbWH6DP jrI42qVjRiwq7NlrpQBrpwDUiHap7At58VQNe3VC+9YU72BE2glwy9bSletgm7xVinkj ZJ377RDXgANCgATpt0LytRD+oGhTmVgvo/9/1PoibocKT4pC6SXPJC83n6Lcm+l5HUfJ DIyKx+GKFSCMJZ8Nne600kLn5yJ16Ts85tOfpc81jFa0EHQ1KkeLXVS4dn40ZwBgbW2R 5fwg==
It's caused by SNAPSHOT.ACC (which I think was distributed together with
> On 15/06/2019 14.03, Uwe Seimet wrote:
> > Hi,
> > Looks as if commit e83f0289 has broken something. My Hatari setup is
> > crashing before the desktop appears. This also happens without AUTO folder.
> > These are the last messages:
> > INFO : GEMDOS HDD emulation, I: <-> /home/us/TT/I.
> > WARN : GEMDOS HD drive I: (may) override ACSI/IDE image partitions!
> > INFO : OS clock ticks / second: 100
> > HDC: READ SECTOR (ACSI, t=0, lun=0, opc=0x8, cnt=0x1, ctrl=0x0) with LBA 0x0 -> OK (0)
> > WARN : No GEMDOS dir '/home/us/TT/C/AUTO'
> > WARN : Bus Error writing at address $ffffff, PC=$fa02dc addr_e3=fa02dc op_e3=4220
> > WARN : Closing 1 & unforcing 0 file handle(s) remaining at program 0x100000e exit.
> > After this there are 2 bombs and a double bus/address error was
> > detected. I added my setup as an attachment.
> I can not reproduce the crash right now with your config file ... but
> PC=$fa02dc indicates that the crash happens within the new clearing
> function, indeed.
> Do you have ACCs on your GEMDOS hard disk? If so, can you try to disable
> them to see whether the crash goes away? And if that's the case, enable
> them one by one again to see which one is causing the crash?