On Mon, 2014-06-16 at 22:24 +0600, Andrey Rahmatullin wrote: > On Sun, Apr 20, 2014 at 02:33:00PM +1200, Jason Alavaliant wrote: > > I believe that linux-image-3.13-1-amd64 3.13.10-1 fixes this problem. I've > > been testing all package updates since > > 3.13.5-1 and this is the first version of 3.13 where I've been able to run > > it for 12 hours+ without tcp dropping out. I only have the computer > > effected by this bug on during the day so can't test longer than 12hours, > > but given in the past the longest it stayed up was sub 2hours I'm fairly > > confident the problem is gone. > Easily reproduced on 3.14.5-1. It may be easy for you, yet other users don't seem to have this problem. Do you also see a similar WARNING message in the kernel log? (Like: "WARNING: CPU: . PID: ... at /build/.../net/core/stream.c:201 inet_csk_destroy_sock+...") Which network driver(s) are you using? Have you applied any router/firewall/bridge/qdisc configuration? Any protocols other than TCP/UDP/ICMP over IP? Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson
Attachment:
signature.asc
Description: This is a digitally signed message part