@retro
the system runs for while then it crashes.
The likely cause of problems is:
Can be L1 cache coherence problem,
or it can also be related to interrupts,
or some strange race condition.
The kernel level debugger that was supposed to be written was not written,
so the problem remains a unknown, for now.
To describe the L1 cache coherence problem:
On a multi core system etch core has its own L1 cache, in this case, it must be synchronized. In order to keep the memory integrity in order.
This will affect things that should behave atomic. (like lib count for example)
it will affect public node lists.
any public structure like execbase or dosbase and so on..
you get the point, if data is not synchronized the result is unpredictable.
if you like you to read up on it, you can here:
https://course.ece.cmu.edu/~ece600/lectures/lecture17.pdf
Last edited by NutsAboutAmiga on 12-Dec-2024 at 10:08 PM.
Last edited by NutsAboutAmiga on 12-Dec-2024 at 10:07 PM.
Last edited by NutsAboutAmiga on 11-Dec-2024 at 09:02 PM.
Last edited by NutsAboutAmiga on 11-Dec-2024 at 09:00 PM.
_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS | 
14 crawler(s) on-line.
138 guest(s) on-line.
0 member(s) on-line.
retro 
