From: "Michael Chan" <mchan@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: "mh+linux-kernel@zugschlus.de" <mh+linux-kernel@zugschlus.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
mcarlson@broadcom.com
Subject: Re: 2.6.26/tg3 ping roundtrip times > 2000 ms on local network
Date: Tue, 19 Aug 2008 10:29:22 -0700 [thread overview]
Message-ID: <1219166962.13090.12.camel@HP1> (raw)
In-Reply-To: <20080819.132040.188336475.davem@davemloft.net>
On Tue, 2008-08-19 at 13:20 -0700, David Miller wrote:
> From: Marc Haber <mh+linux-kernel@zugschlus.de>
> Date: Tue, 19 Aug 2008 19:20:19 +0200
>
> [ netdev added to CC: ]
>
> > I have one HP DL 140 G1 running with Debian stable and a
> > locally-built, vanilla kernel. With 2.6.25.11, everything is fine.
> >
> > But, after updating to 2.6.26.2, I noticed that pinging the host on
> > the local ethernet sometimes (e.g. several times a minute, but not
> > always) results in a round-trip time of larger than two seconds. The
> > packets are not lost though, they're only severly delayed. For an ssh
> > session to the host, this feels like somebody rocking a bad network
> > connector. The same behavior is visible with 2.6.26 and 2.6.26.1.
> >
> > Going back to 2.6.25.11 immediately fixes the issue for me.
> >
> > Syslog doesn't say anything conspicious, unfortunately. As I don't
> > have local access to the box, I cannot say whether it's only the
> > network that freezes or whether it's the entire box.
> >
> > Does it make sense to test any later 2.6.25.x kernel, or is there any
> > post-2.6.26 patch available that may fix the issue for me?
> >
> > Strangely, another DL 140 from the same charge runs just fine with
> > 2.6.26.2.
> >
The may be the 2.5 second polling that was mistakenly added to the code
instead of the intended 2.5 msec.
It has been fixed a few days ago in the net-2.6 tree:
tg3: Fix firmware event timeouts
and it should be in Linus' tree very soon. This reminds us to send the
same patch to -stable.
Thanks.
next prev parent reply other threads:[~2008-08-19 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080819172019.GA5823@torres.zugschlus.de>
2008-08-19 20:20 ` 2.6.26/tg3 ping roundtrip times > 2000 ms on local network David Miller
2008-08-19 17:29 ` Michael Chan [this message]
2008-08-19 22:14 ` Marc Haber
2008-08-19 22:30 ` Matt Carlson
2008-08-20 17:47 ` Marc Haber
2008-08-20 14:11 ` Michael Chan
2008-08-21 16:09 ` Marc Haber
2008-08-21 16:21 ` Michael Chan
2008-08-22 11:33 ` Marc Haber
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=1219166962.13090.12.camel@HP1 \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=mh+linux-kernel@zugschlus.de \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox