> Thats a TCP/scheduling bug in 2.1.x - someone modified the algorithms
> used to schedule wakeups without really understanding the "deep magic"
> in the 2.0.x one. Im assuming it'll get fixed
This is supposed to be fixed in 2.1.129. David checked a fix for it
into vger a few days ago. If anyone still sees it on 2.1.129+ please
report.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/