From: Willy Tarreau <willy@w.ods.org>
To: Thomas Mierau <tmi@wikon.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-ac4 IRQ messup?
Date: Tue, 6 Aug 2002 10:39:43 +0200 [thread overview]
Message-ID: <20020806083943.GA32229@alpha.home.local> (raw)
In-Reply-To: <200208061014.13619.tmi@wikon.de>
On Tue, Aug 06, 2002 at 10:14:30AM +0200, Thomas Mierau wrote:
> the ping on eth0
> The blocks of 5 return at the same time , as the time differnce is always
> 1sec off look pretty nasty
I think you get intreface resets. I had such a problem with a 3c575CB (same
driver), connected to a defective chipset. I couldn't send high traffic
rates, but could receive. There is a watchdog timeout that you can reconfigure
in the 3c59x driver (I don't remember its name, use modinfo). If you reduce
the timeout, you should see reduced drifting in the pings. I used 300ms I
think. But IMHO, that's definitely not a timing problem. Perhaps in your
case, it's simply a half/full duplex misconfiguration.
Regards,
Willy
> PING 192.168.47.47 (192.168.47.47) from 192.168.47.11 eth0: 56(84) bytes of
> data.
> 64 bytes from 192.168.47.47: icmp_seq=1 ttl=255 time=912 ms
> 64 bytes from 192.168.47.47: icmp_seq=2 ttl=255 time=4912 ms
> 64 bytes from 192.168.47.47: icmp_seq=3 ttl=255 time=3912 ms
> 64 bytes from 192.168.47.47: icmp_seq=4 ttl=255 time=2912 ms
> 64 bytes from 192.168.47.47: icmp_seq=5 ttl=255 time=1912 ms
> 64 bytes from 192.168.47.47: icmp_seq=6 ttl=255 time=912 ms
> 64 bytes from 192.168.47.47: icmp_seq=7 ttl=255 time=4905 ms
> 64 bytes from 192.168.47.47: icmp_seq=8 ttl=255 time=3905 ms
> 64 bytes from 192.168.47.47: icmp_seq=9 ttl=255 time=2905 ms
> 64 bytes from 192.168.47.47: icmp_seq=10 ttl=255 time=1905 ms
> 64 bytes from 192.168.47.47: icmp_seq=11 ttl=255 time=905 ms
> 64 bytes from 192.168.47.47: icmp_seq=12 ttl=255 time=4912 ms
> 64 bytes from 192.168.47.47: icmp_seq=13 ttl=255 time=3911 ms
> 64 bytes from 192.168.47.47: icmp_seq=14 ttl=255 time=2912 ms
> 64 bytes from 192.168.47.47: icmp_seq=15 ttl=255 time=1912 ms
> 64 bytes from 192.168.47.47: icmp_seq=16 ttl=255 time=912 ms
> 64 bytes from 192.168.47.47: icmp_seq=17 ttl=255 time=4902 ms
> 64 bytes from 192.168.47.47: icmp_seq=18 ttl=255 time=3902 ms
> 64 bytes from 192.168.47.47: icmp_seq=19 ttl=255 time=2902 ms
> 64 bytes from 192.168.47.47: icmp_seq=20 ttl=255 time=1902 ms
> 64 bytes from 192.168.47.47: icmp_seq=21 ttl=255 time=902 ms
next prev parent reply other threads:[~2002-08-06 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 21:03 Heavy Clock-Drift after update from Kernel 2.4.9 to 2.4.19 Matthias Schniedermeyer
2002-08-05 22:26 ` Alan Cox
2002-08-05 22:17 ` Matthias Schniedermeyer
2002-08-06 8:14 ` 2.4.19-ac4 IRQ messup? Thomas Mierau
2002-08-06 8:39 ` Willy Tarreau [this message]
2002-08-06 9:39 ` Thomas Mierau
2002-08-06 10:01 ` Willy Tarreau
2002-08-06 14:44 ` Thomas Mierau
2002-08-06 16:50 ` Henning P. Schmiedehausen
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=20020806083943.GA32229@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tmi@wikon.de \
/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