Interrupt handler API changed in 2.6.19

Hello Hippo,

I'm sorry but I haven't had the time to look into this since I initially did the port (before X-mas). I chickened out and rolled back to 2.6.18...

One thing I noticed is that the proc-behaviour of processes started from init/sh is exactly as for kernel-processes (started by kthread_run, e.x kjournald), so I suspected that this issue could be related to the new kernel_execve call (starting with v2.6.19 init is started with kernel_execve() instead of using the execve syscall).

But if it is so, this issue would (possibly) also apply to other architectures, and I have not seen any bug reports anywhere.