Skip to contentSkip to conversation

2.6.29 Networking Problems

DISCUSSION Michael B. Trausch 3 participants 3 messages Mar 27, 2009

lore
Share & tools
lore
#0 lore raw

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
#1 lore raw
Quoted 15 lines · Michael B. Trausch

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.

Quoted 6 lines

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

I'll second this on 2.6.29. Asus M2N SLI Deluxe mobo, quad core phenom, 4GB ram.

When I woke up this morning I had no network. Ifconfig said it was up and ok, but I couldn't even ping my router. So I went to another machine and the router etc was fine. Restarting the networking did not help. The leds on the mobo jacks were on so the MCP55's hadn't been killed. A reboot that took a good piece of an hour cuz it had timed out on 1.5 TB of drives and had to fsck them, and its been fine since.

Quoted 5 lines

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

Signature · 6 lines
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Windows without the X is like making love without a partner.
	-- MaDsen Wikholm, [email protected]