E-UAE Crashing with OS4.1 [SOLVED]

Hi,

It was mentioned in one of the other forums that some are having problems with UAE and OS4.1 - myself included.

I went back to using version 0.28 but that did not help me.

I have tried UAE when booting from my old OS4 partition (using OS4.1 kickstart - not recommended I know but it was a quick dirty test) and everything works fine. UAE starts as it should and all the games I use from GL-UAE fire up fine. Yet when I boot from my OS4.1 partition I get crashes, first a DSI which if you click through becomes an ISI.

Now I *can* launch UAE and get it to come up with the basic load a floppy screen. I had to download an ADF to try as I normally run things from hard disk, and when I loaded it using ctrl-altF1 it fires up and runs fine.

Yet anything I try to run from the hard disk using filesystem2 crashes immediately. This includes all the GL-UAE launched games and even a fresh install of OS3.1 I tried especially for the purpose.

Are those who can get UAE to run on OS 4.1 just using ADF files and not using GL-UAE and hard disk based folders ?

Any ideas as to why UAEcrashes when trying to read a hard disk folder but worksfine with OS4.0 ?

I am missing SlamTilt

Edit: Someone previously suggested that the stack needs to be raised, I am using 500000 which should surely be more than enough ?


Bill.

@BillE

Did you read this thread?
Might have some hints...

@BillE

For me, E-UAE was crashing on launch while it was reading the config file.

I followed the advice of salass00 in post #87 of that thread ...

Quote:

Stack size 32768.

I am using E-UAE 0.8.29-WIP3-SDL.

Nothing fancy, I'm emulating a 68000 CPU and using AmigaOS 3.1 ROM and AmigaOS3.1. My Workbench is a drawer in my E-UAE drawer on my hard drive. Using the same config file I have used since OS4 update 4.

---
redfox
?A1-C (750GX) + AmigaOS 4.1

Why does nobody post crashlogs if there are crashes?

@Jack

Quote:

Of course. "It was mentioned in one of the other forums that some are having problems with UAE and OS4.1"

In fact I mentioned some of the hints from that thread - they don't help BTW.

The problem with the other thread is it covers ALL problem software with OS4.1 so it is difficult to find the relevant replies to anything UAE related.

So I started a new thread in this forum as it IS about UAE ! Seemed a better idea

And so far E-UAE is the *only* problem area I have come across since installing OS4.1.


Bill

@Capehill

I am waiting for someone to reply that will be able to do something with them.

I hate reading forum posts with long crashlogs in them and assume others would not like it either. There is little point posting them in this text as most reading it will just scroll past it to the next message. I certainly do !

Hopefully Evil Rich will read this then I can send him some crashlogs.


Bill.

@BillE

Understood, but usually the register list + stacktrace is not very long IMHO.

Just in case anyone can be bothered to read it a short version of the crashlog is below. I can post the full thing to anyone who understands the ruddy things.

The "nan" (not a number) in the FPU register looks like the culrpit but how it gets there I have no idea myself.

Any ideas ?

I only get this when trying to boot the emulator using a filesystem2 command - which works fine with OS4.0 BTW.


BTW, I included the CPU info just to show off


Bill.


===================================================
Crash log for task "uae"
Generated by GrimReaper 52.7
Crash occured in module kernel at address 0x014401D0
Type of crash: DSI (Data Storage Interrupt) exception

Register dump:
GPR (General Purpose Registers):
0: 014401D0 68716000 00000000 6FF91000 80000007 687160D8 687160D8 0000000B
8: 687162A7 014402B8 00000000 00000000 35333255 FFE4E4E4 64F013B8 64E80000
16: 64FE58E0 01DA0000 00000000 68716299 01DA63E6 0000001C FFFFFFFE 0000000F
24: 00000000 00000020 687160D8 01C924CC 80000006 01C92C08 00000020 00000001


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 1177 48 1
4: 1 86.8 76.8 1
8: 1 -0.00392924 86.8 76.8
12: 1263 124 0 0
16: 0 0 0 0
20: 0 0 0 0
24: 0 0 0 0
28: 0 0 0 0

FPSCR (Floating Point Status and Control Register): 0x82004000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0000F030
Condition (cr) : 0x35333255
Instruction Pointer (ip) : 0x014401D0
Xtended Exception (xer) : 0xC000E161
Count (ctr) : 0x014401D0
Link (lr) : 0x014402DC
DSI Status (dsisr) : 0x42000000
Data Address (dar) : 0x68715FD0



680x0 emulated registers:
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x014401D0 belongs to module "kernel" (HUNK/Kickstart)

Stack trace:
native kernel module kernel+0x000401d0
native kernel module kernel+0x0001853c
native kernel module kernel+0x000184d4
native kernel module kernel+0x00016c94
native kernel module kernel+0x00016dfc
native kernel module dos.library.kmod+0x00010f20
native kernel module dos.library.kmod+0x00032ee8
native kernel module dos.library.kmod+0x00033770
native kernel module dos.library.kmod+0x00014350
module uae at 0x7EE011B8 (section 5 @ 0x29A198)
module uae at 0x7EDD0A60 (section 5 @ 0x269A40)
module uae at 0x7EDD0EE0 (section 5 @ 0x269EC0)
module uae at 0x7EB9C01C (section 5 @ 0x34FFC)
module uae at 0x7EB9C2EC (section 5 @ 0x352CC)
module uae at 0x7EB9D4C8 (section 5 @ 0x364A8)
module uae at 0x7EB9DBD0 (section 5 @ 0x36BB0)
module uae at 0x7EB67B9C (section 5 @ 0xB7C)
module uae at 0x7EDEC3BC (section 5 @ 0x28539C)
module uae at 0x7EE049E0 (section 5 @ 0x29D9C0)
module uae at 0x7EE04D30 (section 5 @ 0x29DD10)
native kernel module dos.library.kmod+0x0001ea6c
native kernel module kernel+0x0003a49c
native kernel module kernel+0x0003a51c


PPC disassembly:
014401c8: 7c0803a6 mtlr r0
014401cc: 4e800020 blr
*014401d0: 9421ffd0 stwu r1,-48(r1)
014401d4: 7c0802a6 mflr r0
014401d8: 90a10008 stw r5,8(r1)

System information:

CPU
Model: Motorola MPC 7447/7457 Apollo V1.2
CPU speed: 1266 MHz
FSB speed: 133 MHz
Extensions: performancemonitor altivec
===================================================

Hi @BillE

Any ideas as to why UAEcrashes when trying to read a hard disk folder but worksfine with OS4.0 ?

What file system is Euae running in? I always used latest SFS for best speed. But the system bootsup in FFS2.

What's changed in the OS4.1 file systems? I don't have os4.1 yet...

For me, I tried Euas_sdl and it works great. A1XE with OS4.1

BUMP

Any ideas yet ?

Is Rich back from AmiWest and able to help ?


Bill.

@Snuffy

I've had to switch my Harddisc files partition back from JXFS to SFS.
AF2006 loads under E-UAE when its HD files are on a JXFS partition but datatypes under E-UAE don't work, moving it back over to an SFS partition worked here.

I have an old FFS partition for my UAE stuff and AOS3.1.

@BillE

Don't know if this will help, because I don't use GL-UAE.

E-UAE running fine using OS4.1 on my ?A1 since September 28, 2008.

I use E-UAE-0.8.29.WIP3-SDL. I just double-click on the uae icon to launch E-UAE. It brings up an AmigaOS 3.1 Workbench screen and I launch my old programs from there.

I use a hard disk based folder called Workbench which becomes my AmigaOS 3.1 DH0: system partition. I also have some ADF files which I occasionally mount as floppies.

These are the only changes I required to make it work:
(uae-sdl icon information)
1) changed Stack size to 32768
2) changed Start from to Workbench

I did not have to modify anything in my .uaerc file.

---
redfox

@BillE

Quote:
What about the latest beta? Have you tried it yet?

Quote:
Here it works fine (once the stack has been set up correctly) in all cases (ADFs, archives, HD folders with or without glUAE).

Quote:
It sounds like E-UAE and AOS4.1 cannot really get along :/

Quote:
Definitely. Using just 32768 here.

saimo

@saimo

Just downloading the latest beta and will give it a go tonight. This may be the version I was originally using - no time to check now work looms

I am not expecting any change as all versions I have tried so far have been fine on OS4.0 (even with OS4.1 KS modules) but crash when booting from OS4.1.

The other strange thing is EUAE works if loading an ADF but I only have one of those I downloaded to test it, but not when running anything from a hard drive folder !
Why would that make any difference ???



Bill.

@BillE

Quote:
This looks exactly how E-UAE started acting up on my system. In fact, somewhere I had even posted a report about it failing to mount a HD partition from a drawer. Then, I found out that the problem was cured by simply raising the stack up a bit.

saimo

@saimo

Quote:

I had the stack at 500,000 which seems high enough. So maybe the stack was not being used ?

I noticed that my UAE icon was set to run from the shell so I changed this to workbench instead. Lo and behold E-UAE could now run from a virtual HD, I loaded up WB 3.1 nio problem.

Running from the shell still proved troublesome as did running using GL-UAE scripts.

I did have a high stack in the GL-UAE icon, more than enough but it seems as this does not get passed to UAE.

I remembered some "Process Stack Size"CK setting in the DOS Prefs which had defaulted to something low like 16kb, I set it higher to 80kb and hit Save. E-UAE even running from GL-UAE then behaved as it should and runs :o)

I just checked on my old OS4 partition and the setting I had previously in the DOS Prefs was 60kb, Looks like I did not copy over my old envarc:sys/dos.prefs after installing OS4.1 and the default value is NOT enough to run UAE.

OK. You will hear no more from me for a while, I have a few hours of Slamtilt to keep me busy for the rest of the day !!!


Bill.

@saimo

Quote:

I had the stack at 500,000 which seems high enough. So maybe the stack was not being used ?

I noticed that my UAE icon was set to run from the shell so I changed this to workbench instead. Lo and behold E-UAE could now run from a virtual HD, I loaded up WB 3.1 nio problem.

Running from the shell still proved troublesome as did running using GL-UAE scripts.

I did have a high stack in the GL-UAE icon, more than enough but it seems as this does not get passed to UAE.

I remembered some "Process Stack Size"CK setting in the DOS Prefs which had defaulted to something low like 16kb, I set it higher to 80kb and hit Save. E-UAE even running from GL-UAE then behaved as it should and runs :o)

I just checked on my old OS4 partition and the setting I had previously in the DOS Prefs was 60kb, Looks like I did not copy over my old envarc:sys/dos.prefs after installing OS4.1 and the default value is NOT enough to run UAE.

OK. You will hear no more from me for a while, I have a few hours of Slamtilt to keep me busy for the rest of the day !!!


Bill.

@BillE

Thanks. The higher stack and running E-UAE from WB instead of from shell worked for me but nothing from GL-UAE woud until I also changed that DOS setting. Now all UAE related stuff works fine.

I wonder if that has any bearing on other DSIs from other programs?


ace