>What networking card are you using?
3com - 3c509 or 3c579
>Also, when you get the machine into such a state of stuck TCP sockets,
>two pieces of data are extremely useful:
>
>1) Whether the kernel is printing out "socket destroy delayed"
> messages into the logs/console.
No consoles to speak of, but the kernel logs are just jam packed with the
above message. I sent them to you directly, some 25k of them, David.
>
>2) Raw /proc/net/tcp output, so that I can see which timers are active
> which should be destroying the sockets after some time.
I'll remember that next time. If I'm lucky, there won't be one. It
effectively turns them into boat anchors, so...
Mike was here...
-
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/