From: Ingo Freund <linux-kernel-news@e-dict.net>
To: linux-kernel@vger.kernel.org
Subject: Re: sometimes very long response times on network interfaces since 2.6.22
Date: Fri, 12 Oct 2007 07:57:01 +0200 [thread overview]
Message-ID: <470F0CAD.2030308@e-dict.net> (raw)
In-Reply-To: <470C7898.1060405@cosmosbay.com>
On 10.10.2007 09:00, Eric Dumazet wrote (please find the answer below the original text):
> Ingo Freund a écrit :
>> Hello,
>>
>> since I switched to kernel 2.6.22 my dell 1750 server
>> with the two onboard BCM5704 network interfaces doesn't
>> work properly anymore.
>> TCP requests sometimes need more than 30 seconds to be answered
>> (or to get away) and the application stops with timeouts.
>> We are talking about two servers connected via Gigabit switch.
>> The timeouts happen up to ten times a day.
>> In the meantime I tried an old 3com 3c905c NIC which showed
>> the same behaviour.
>> I still couldn't figure out in which special situation the
>> communication stops.
>> The only solution ist to boot the old 2.6.21.5 kernel.
>> With this, all runs fine.
>> Did I miss a config issue in the migration to 2.6.22?
>> The machines run in a productive environment and there is
>> not much room (time) to debug, but if needed, I could try
>> if anyone would need more information for help.
>>
>
> Hi
> 1) A tcpdump would help for sure...
> 2) Could you try 2.6.23
> -
I'm trying 2.6.23 with the same config as 2.6.22.n since yesterday.
The error after on day uptime didn't show up again.
It seems that 2.6.22.n is buggy in some special conditions
concerning high load network traffic. This is not depending on
the used NIC.
Thanks for reading this.
-Ingo.
prev parent reply other threads:[~2007-10-12 5:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 6:33 sometimes very long response times on network interfaces since 2.6.22 Ingo Freund
2007-10-10 7:00 ` Eric Dumazet
2007-10-10 9:03 ` Ingo Freund
2007-10-13 0:39 ` Andrew Morton
2007-10-12 5:57 ` Ingo Freund [this message]
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=470F0CAD.2030308@e-dict.net \
--to=linux-kernel-news@e-dict.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox