On Apr 13 2019, Eero Tamminen <o...@helsinkinet.fi> wrote: > I still get sometimes: > --------------------------------------------------- > Data read fault at 0x801740c4 in Super Data (pc=0x2918) > BAD KERNEL BUSERR > Oops: 00000000 > PC: [<00002918>] auto_inthandler+0x0/0x28 > SR: 2400 SP: (ptrval) a2: 8017a478 > d0: 00000018 d1: 0000001a d2: 00000000 d3: 8017a480 > d4: 00000018 d5: 00000054 a0: 8017a480 a1: 8016f84c > Process exe (pid: 26, task=(ptrval)) > Frame format=B ssw=0345 isc=2f00 isb=48e7 daddr=801740c4 dobuf=80176e58 > baddr=801740c4 dibuf=801740c4 ver=0 > Stack from 009b9ff8: > 02088001 ebf40070 > Call Trace: > Code: 0005 61ff 0002 c926 508f 588f 60a2 0000 <42a7> 4878 ffff 2f00 48e7 > 7ce0 200f 0280 ffff e000 2440 2452 e9ef 010a 0032 0440 > ... >> d auto_inthandler > auto_inthandler: > $00002918 : 42a7 clr.l -(sp) > $0000291a : 4878 ffff pea $ffffffff.w > $0000291e : 2f00 move.l d0,-(sp) > $00002920 : 48e7 7ce0 movem.l d1-d5/a0-a2,-(sp) > --------------------------------------------------- > >>2GB address in stack, which the autovector handler tries to clear?
This is a *read* fault. The emulation appears to be severely confused. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
