linux-kernel - 2.6.29 Networking Problems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID:  <20090326232045.700a251a@zest.trausch.us>
Date:	Thu, 26 Mar 2009 23:20:45 -0400
From:	"Michael B. Trausch" <mike@...usch.us>
To:	linux-kernel@...r.kernel.org
Subject:  2.6.29 Networking Problems

Alright, so I upgraded to 2.6.29 and had all sorts of issues with my
networking (x86-64 system, both forcedeth and 3c59x NICs).  At first I
thought my forcedeth NIC was dying or something, so I disabled it and
installed a trusty 3com.  When it started acting up also, I began to
suspect software, and some searching led me to the thread (and
eventually the patch) at:

  http://patchwork.kernel.org/patch/14465/

So, I applied this patch to my local kernel, and my test (transferring
13 GiB of data over the LAN) now can be run repeatedly.  Prior to
applying the patch, I'd start the transfer and it'd go for about 20
seconds and all transfer would stop, and ping would not return errors,
just nothing.

Any chance that this patch will land in 2.6.29.1?  Or other code that
fixes the same problem?  I haven't tried it against Linus' kernel tree
yet because I probably won't run that kernel again until at least -rc2
or -rc3, so apologies if this issue is already fixed in the trunk.

	--- Mike

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/