lkml.org 
[lkml]   [2002]   [Aug]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 2.4.19-ac4 IRQ messup?
Date
Thanks,
I looked it up its called watchdog (what else). It was set to 5000ms and I
changed it to 300ms. But the result is : no change!
I can see the transmit and receives on the switch. The problem must be the
receive part of the transceiver.
I ran mii-diag and it reports that it is set up for full duplex 100Mbit and
has a link. So that reports back ok.
Any other ideas ?

Am Dienstag, 6. August 2002 10:39 schrieb Willy Tarreau:
> 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

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:27    [from the cache]
©2003-2011 Jasper Spaans