Hello All, I have got an interesting lock up situation using 2.6.21.5 kernel together with rt15 patch. I'll try also with 22.1 before that i wanted to check if anybody else has faced it. I have one application communicating with a kernel driver. A character driver has been implemented as an interface. The situation is a classic provider-consumer case. Kernel driver provides data and application consumes it. I have difficulties with triggering the application. The provider receives a frame from the network and feeds this into the application. The proiroities are configured with the following script: So hrtimer has the highest priority with 99 and net-rx and net-tx is configured with 55. The application is configured for 70. The application runs smoothly for a while and then, the computer completely locks up. I am unable to enter any keyboard data. When i unplug the network cable, i see the message that it has been disconnected. So, the kernel driver is still alive. What could be the reason for this lock up. I also tried with round robin policy. It has been much more stable but it also locks up after a while. Thanks and regards, Sinan. - To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
