TCP still hangs w/2.0.34pre16

Jim Wilcoxson (jim@meritnet.com)
Sat, 23 May 1998 16:26:26 -0700

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Vadim E. Kogan: "Re: Possible cause of "spurious APIC interrupt""
Previous message: Michal Jaegermann: "Re: 2.0.34p15 bugs? (probably 2.1 too)"

We've been having web server hangs since 2.0.32. I upgraded to 2.0.34pre16
yesterday hoping the hangs would go away, but no luck. The web server is
threaded (AOL server, and please, no flames :-)

Here's netstat -a output if that helps:

tcp 0 0 (my hostname) BayArea56k469.Net:63643 FIN_WAIT2
tcp 0 0 (my hostname) BayArea56k469.Net:63645 FIN_WAIT2
tcp 0 0 (my hostname) BayArea56k469.Net:63646 FIN_WAIT2
tcp 0 0 (my hostname) BayArea56k469.Net:63652 FIN_WAIT2

This seems to happen more often from one of our laptops than from the
other; both are running Win 95 with patches and service packs, though
patching Windows feels like "Hmmm... wonder what I have now?"

Any advice on how to track this down better?

Thanks,
Jim

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

Next message: Vadim E. Kogan: "Re: Possible cause of "spurious APIC interrupt""
Previous message: Michal Jaegermann: "Re: 2.0.34p15 bugs? (probably 2.1 too)"