From: Gene Heskett <gene.heskett@verizon.net>
To: "Michael B. Trausch" <mike@trausch.us>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.29 Networking Problems
Date: Thu, 26 Mar 2009 23:47:19 -0400 [thread overview]
Message-ID: <200903262347.19338.gene.heskett@verizon.net> (raw)
In-Reply-To: <20090326232045.700a251a@zest.trausch.us>
On Thursday 26 March 2009, Michael B. Trausch wrote:
>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
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.
>--
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
--
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, mwikholm@at8.abo.fi
next prev parent reply other threads:[~2009-03-27 3:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 3:20 Michael B. Trausch
2009-03-27 3:47 ` Gene Heskett [this message]
2009-03-27 5:04 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903262347.19338.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@trausch.us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®