With the current kernel I've noticed a strange behaviour. When running CPU-hogs like gcc, the AES is very unresponsive. Actually, it's completely locked. It didn't use to be like that, previously I could continue using other applications while compiling the kernel, although at a reduced pace. /* ** Jo Even Skarstein http://home.nvg.org/~joska/ */