From: ben soo <lnx-kern@soo.com>
To: Kernel Mailing list <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Network sky2 Module
Date: Thu, 20 Sep 2007 02:43:30 -0400 [thread overview]
Message-ID: <46F21692.4020607@soo.com> (raw)
In-Reply-To: <20070918080525.7a49d110@freepuppy.rosehill.hemminger.net>
>> ben soo wrote:
[...]
>>> This last might be an artifact caused by the firewall, i dunno.
[...]
> Bill Davidsen <davidsen@tmr.com> wrote:
>> Yes, I have found that I get far less problem in this area leaving the
>> MTU at 1500, then putting a larger MTU (usually 9000) into the routing
>> table for segments, or even just machines, where I know there is direct
>> connectivity.
[...]
Stephen Hemminger wrote:
> If you want to use Jumbo frames, you need to have routers and firewalls
> that correctly handle ICMP and do path MTU discovery. If you have bridges
> or firewalls that aren't Jumbo aware on both interfaces, then there will
> be long timeouts retries for each connection. If you have busted routers
> and firewalls that swallow ICMP then PMTU won't work well either.
i turned off the motherboard Marvell Gbit devices and installed a
Realtek 8169 card, all the while keeping to kernel version
2.6.23-rc6, and saw all the network problems go away. Must mean it
was a sky2 driver bug.
Am currently running 2.6.23-rc7 on the affected server and the rc7
sky2 driver is holding up fine so far.
thank you!
b
next prev parent reply other threads:[~2007-09-20 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 15:14 PROBLEM: Network sky2 Module Werner Meurer
2007-09-18 4:02 ` ben soo
2007-09-18 14:28 ` Bill Davidsen
2007-09-18 15:05 ` Stephen Hemminger
2007-09-20 6:43 ` ben soo [this message]
2007-09-23 1:56 ` PROBLEM: Network sky2 Module, kernel version 2.6.23-rc7 ben soo
2007-09-24 6:06 ` Stephen Hemminger
2007-09-28 22:48 ` Bill Davidsen
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=46F21692.4020607@soo.com \
--to=lnx-kern@soo.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.