From: Thomas Quinot <thomas@cuivre.fr.eu.org> Date: Thu, 9 Jan 2003 11:17:48 +0100 The simple program below crashes recent 2.4 kernels. The network stack appears to enter a busy loop; messages from the rate limiting system are emitted to the console: NET: XXXXX mesages suppressed Type 'dmesg' and you'll see the rest of the messages. It works perfectly fine for me, the message the kernel is spitting out is: TCP(foo:735): Application bug, race in MSG_PEEK. And it doesn't hang no matter how I run your test program. You'll need to figure out what is specific to your system if it really does hang. Another idea is to get register dumps using SySRQ and figure out where in the kernel the cpu is when your box 'hangs'. - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
