Hi, I have a uniprocessor system that deadlocks upon loading of a module. This module uses some spinlocks at various points. Unfortunately my arch does not support non-maskable interrupts. I have enabled spinlock debugging in the kernel, but the system deadlocks before I see any spinlock related printks. My approach is to spot and fix the problem reading the code, rather than searching for clues at run-time. Do you have any suggestions to what to look for in the code this way? I replaced spin_lock() functions with irq disabling versions to cover for potential races from irqs. But the problem is still there. I will also check whether a lock is acquired twice. If I replaced all spinlocks with spin_trylocks would that help to at least spot recursive locks? What else should I look for? Thanks, Bahadir -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
