Deadlock after the insmod I did a network layer firewall, it is loaded to the kernel using insmod order rules, started smoothly, and also the normal operation of the firewall. But I have been testing -- after loading a certain number of first insmod order can no longer proceed in a fight on the lockup. Deadlock situation is "keyboard kept three lights flickered and then all operators unable to respond." This situation seems to be more common lockup, but why such a situation will happen after I insmod, expert help. Deadlock after the insmod Preliminary estimates keyboard is not detected problems, I will not be too many insmod, washed the keyboard stuff ah? If so how to resolve, please help! ! ! Deadlock after the insmod But did not know? Deadlock after the insmod Kernel programming is indeed very troublesome state, I am now in the Linux kernel under the state program. And you do not like is that I do not firewall, I am doing is routing. Some time ago I loaded modules (insmod *.o) when the regular lockup. Later, I found that is the hook (hook) did not hang up properly. Deadlock appeared this situation, the basic process is the best process over again, and see if it is in some places fewer exit (0), return ah procedures similar to those from the language, there is also a look at the function of the joints, and so on target areas is not kidding. [ Closed window ]