@umisef

C is a crappy language. That's why I prefer E normally

I agree with both your comments. There is something fishy in the system. It actually seems to happen more often, or possibly only on AmigaOnes, not on SAMs.

I'll try to debug my system to see if I can make it stop and what module or program might be causing it. However, it could still be a bug in the Grim Reaper because other than killing programs my system is stable and I never get 0100000F except when IBrowse crashes and I click Continue (no surprise there..). So I don' think the memlist is corrupted prior to this.

Stripping the startup would probably only shorten the memlist and hide the bug in the Reaper too

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@umisef

Quote:

Stick it into various places during bootup, and narrow down at exactly what point the memory list gets corrupted, and what address exactly gets corrupted.

Actually a simpler way right now would be to enable a greater debug level in the kernel. UBoot rRefs Kernel command line Deniil715.

Quote:

From then on, things are a lot easier when running under emulation

It would if OS4 ran on top of Linux like some people thought it did.

@umisef
Quote:

Was the cause for the display-corruption-when-not-using-debug-kernel-on-SAM ever identified and fixed? Or did that just happen to go away when some module sizes changed? Because it sure sounds like something deep in the heart of OS4's startup is corrupting memory somewhere...

As of Update2 and the latest SAM UBoot the problem has disappeared here. Problems created by activating 1GB memory are also gone. In fact, my SAM now seems more stable than my µA1.

_________________
X1000 with 2GB memory & OS4.1FE