Re: [hatari-devel] Hatari and OUTSIDE (virtual memory manager)

[ Thread Index | Date Index | More Archives ]

Le 04/10/2018 à 12:22, Uwe Seimet a écrit :

OUTSIDE does not crash anymore when being started, but it still does not
work. When starting NVDI Hatari freezes, does not even react when
pressing F12. Even Ctrl-C could not kill it, I had to use the kill
command. Without NVDI OUTSIDE can be started, but the system is not
stable, often there are double bus faults.

ROMSPEED now crashes Hatari:

#0  0x00007ffff5b81fa0 in raise () from /lib64/
#1  0x00007ffff5b83b7d in abort () from /lib64/
#2  0x000055555586f5ef in __pushtry (j=<optimized out>)
     at /home/us/hatari/hatari/src/cpu/cpummu.c:1743
#3  0x000055555601e8bb in __pushtry (j=<optimized out>)
     at /home/us/hatari/hatari/src/cpu/cpummu.c:1736
#4  0x000055555591e47c in fill_icache030 (addr=addr@entry=14684700)
     at /home/us/hatari/hatari/src/cpu/newcpu.c:10786
#5  0x0000555555930b74 in fill_prefetch_030_ntx ()
     at /home/us/hatari/hatari/src/cpu/newcpu.c:12089
#6  0x0000555555932425 in fill_prefetch_030 ()
     at /home/us/hatari/hatari/src/cpu/newcpu.c:12236
#7  fill_prefetch () at /home/us/hatari/hatari/src/cpu/newcpu.c:12256
#8  0x0000555555932b79 in Exception_mmu030 (oldpc=<optimized out>, nr=11)
     at /home/us/hatari/hatari/src/cpu/newcpu.c:3603

I noticed that this code fragment:

if (eamode == 0 || eamode == 1 || eamode == 3 || eamode == 4 || eamode =
= 6 || (eamode == 7 && rreg > 1))

is present in cpummu030.c and also in newcpu.c, but the changes only refer to
one of these files?

only cpummu030.c needs to be changed (see the patch I sent you today)

When testing I had both prefetch and cycle exact enabled.

I can't get a crash when I use your config file you posted with the nvdi issues. I run :

../hatari -c ../tests/hatari_uwe.cfg -d /others/ST/D/ --tos ~/Emul/ST/tos/tos306fr.img

Once desktop appears, I run romspeed (that I copied into /others/ST/D) and it works in all cases, with or without cycle exact.

Maybe your config is autostarting some other programs that create this failure ? Can you try to start with only a gemdos HD drive containing only romspeed ?

Or start with an empty hatari.cfg ("touch hatari.cfg") and add all the parameters on the command line ?

And just to be sure, did you do a "make clean" before compiling, just in case some old code was still present ?


Mail converted by MHonArc 2.6.19+