This is a problem in certain unusual states of the TCP/IP-stack. Since many users experience the deadlock with wireless and/or dialup connections, this might be the right one to look at, since sequence holes are something that might typically occur on such connections.
Can a developer please tell me, whether this patch is already applied to 2.6.24-19 ? If no, would it be possible to provide a testing kernl with this patch applied?
OK, after all this mess, I skimmed through the 2.6.25 changelogs looking for possible deadlock fixes.
The first commit that seems to be conistent with my own experience is:
http:// git.kernel. org/?p= linux/kernel/ git/torvalds/ linux-2. 6.git;a= commitdiff; h=b000cd3707e7b 25d76745f9c0e26 1c23d21fa578
This is a problem in certain unusual states of the TCP/IP-stack. Since many users experience the deadlock with wireless and/or dialup connections, this might be the right one to look at, since sequence holes are something that might typically occur on such connections.
Can a developer please tell me, whether this patch is already applied to 2.6.24-19 ? If no, would it be possible to provide a testing kernl with this patch applied?
TIA,
Wolfgang