Hi All, I've corrected the syscall portion of the pipeline, and have a new, but similar, problem. The ADEOS_SYSCALL_PROLOGUE event (event 4 on this system) is now branching to __adeos_enter_syscall function, which calls adeos_handle_event. This eventually returns to the kernel, marked as to be handled via the linux syscall code. This starts a long loop of event 4's, which are apparently not being processed correctly. I get this behavior when trying to load the rtai_nucleus module, or run the latency example. What syscall event does this adeos event 4 correspond to? What generated it? FYI, when I modify entry.S to call a .do_show_syscall for this event what I get is: syscall 3221225472 ( f7db7000, 1000, 1000, f7db8000, fe92d50, 100000000200f932) regs=c00000000065aefc current=c00000007983b1c0 cpu=0 Which is : syscall gpr0 ( r3, r4, r5, r6, r7, r8) r9(ptr to regs) current_task cpu# Thanks, Terry
[Adeos-main] ppc64 pipeline problem
Reynolds, Terry \(Contractor-SIMTECH\) Thu, 24 Mar 2005 18:01:59 +0100
