On Wed, Jun 18, 2014 at 05:11:41PM +0100, Ben Hutchings 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. Sure. > 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+...") Yes, see https://bugzilla.kernel.org/show_bug.cgi?id=78121 > Which network driver(s) are you using? r8169 > Have you applied any router/firewall/bridge/qdisc configuration? Any > protocols other than TCP/UDP/ICMP over IP? I have a bridge with one interface in it (and there are bridge.ko functions in the WARNING stack). Otherwise nothing special. Note that I couldn't reproduce this on a custom-built vanilla 3.15. -- WBR, wRAR
Attachment:
signature.asc
Description: Digital signature