> it looks like there's some bug in the TCP stack of
> at least 2.3.5.
After looking closely, I have seen what seems to be
a LIFO problem, so it might have something to do with
bottom halves not getting run (or another LIFO order
which I'm unaware of).
When the symptoms occur, network packets are in the
'out' queue for several _minutes_, until the kernel
comes around to sending them -- even on an almost
empty line this problem occurs!
Active Internet connections (w/o servers)
0oto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 64 agratax.demon.nl:1287 k052r.balpol.tudelf:cvs ESTABLISHED
tcp 0 9 agratax.demon.nl:1286 humbolt.nl.linux.o:pop3 ESTABLISHED
tcp 0 0 agratax.demon.nl:1284 k052r.balpol.tudelf:cvs TIME_WAIT
tcp 0 6170 agratax.demon.nl:1274 terra.geo.uu.nl:smtp ESTABLISHED
tcp 0 0 agratax.demon.nl:1231 pluto.news.demon.n:nntp ESTABLISHED
tcp 0 0 localhost:7100 localhost:1028 ESTABLISHED
tcp 0 0 localhost:1028 localhost:7100 ESTABLISHED
The '6170' above has been there for almost 10 minutes (!),
while newer traffic seems to run without too much problems.
The newer '64' seems to have problems as well though :(
This simply kills TCP connections. Somebody still awake
should probably code an emergency patch so that a fix is
available before Europe wakes up again :)
Rik -- Open Source: you deserve to be in control of your data.
+-------------------------------------------------------------------+
| Le Reseau netwerksystemen BV: http://www.reseau.nl/ |
| Linux Memory Management site: http://www.linux.eu.org/Linux-MM/ |
| Nederlandse Linux documentatie: http://www.nl.linux.org/ |
+-------------------------------------------------------------------+
-
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/