Packet lag with kernel 2.3.99.pre6-3?

From: Erik van Asselt (assie@casema.net)
Date: Tue Apr 25 2000 - 17:01:24 EST

Next message: Borislav Deianov: "Re: SCHED_RR is broken + patch"
Previous message: Russell King: "Patch: busmouse.c - more doc and spinlock optimisation"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I'm using pre6-5 now and still having problems with severe lag pinging
my
ethernet adres 192.168.2.2 or my real internet adres.
pinging localhost seems to ping fine.
is this a kernel bug or did i something wrong?

--
PING 192.168.2.2 (192.168.2.2) from 192.168.2.2 : 56(84) bytes of data.
64 bytes from 192.168.2.2: icmp_seq=0 ttl=255 time=0.1 ms
64 bytes from 192.168.2.2: icmp_seq=1 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=2 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=3 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=4 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=5 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=6 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=7 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=8 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=9 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=10 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=11 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=12 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=13 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=14 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=15 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=16 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=17 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=18 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=19 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=20 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=21 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=22 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=23 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=24 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=25 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=26 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=27 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=28 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=29 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=30 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=31 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=32 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=33 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=34 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=35 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=36 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=37 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=38 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=39 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=40 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=41 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=42 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=43 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=44 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=45 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=46 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=47 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=48 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=49 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=50 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=51 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=52 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=53 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=54 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=55 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=56 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=57 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=58 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=59 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=60 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=61 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=62 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=63 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=64 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=65 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=66 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=67 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=68 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=69 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=70 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=71 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=72 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=73 ttl=255 time=9130.1 ms
64 bytes from 192.168.2.2: icmp_seq=74 ttl=255 time=8290.0 ms
64 bytes from 192.168.2.2: icmp_seq=75 ttl=255 time=7470.0 ms
64 bytes from 192.168.2.2: icmp_seq=76 ttl=255 time=6590.0 ms
64 bytes from 192.168.2.2: icmp_seq=77 ttl=255 time=5660.1 ms
64 bytes from 192.168.2.2: icmp_seq=78 ttl=255 time=4760.1 ms
64 bytes from 192.168.2.2: icmp_seq=79 ttl=255 time=3830.1 ms
64 bytes from 192.168.2.2: icmp_seq=80 ttl=255 time=2940.0 ms
64 bytes from 192.168.2.2: icmp_seq=81 ttl=255 time=2020.0 ms
64 bytes from 192.168.2.2: icmp_seq=82 ttl=255 time=1170.0 ms
64 bytes from 192.168.2.2: icmp_seq=83 ttl=255 time=270.1 ms
64 bytes from 192.168.2.2: icmp_seq=84 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=85 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=86 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=87 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=88 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=89 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=90 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=91 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=92 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=93 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=94 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=95 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=96 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=97 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=98 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=99 ttl=255 time=9140.1 ms
64 bytes from 192.168.2.2: icmp_seq=100 ttl=255 time=8250.1 ms
64 bytes from 192.168.2.2: icmp_seq=101 ttl=255 time=7370.0 ms
64 bytes from 192.168.2.2: icmp_seq=102 ttl=255 time=6510.1 ms
64 bytes from 192.168.2.2: icmp_seq=103 ttl=255 time=5589.9 ms
64 bytes from 192.168.2.2: icmp_seq=104 ttl=255 time=4710.1 ms
64 bytes from 192.168.2.2: icmp_seq=105 ttl=255 time=3830.1 ms
64 bytes from 192.168.2.2: icmp_seq=106 ttl=255 time=3030.1 ms
64 bytes from 192.168.2.2: icmp_seq=107 ttl=255 time=2270.1 ms
64 bytes from 192.168.2.2: icmp_seq=108 ttl=255 time=1390.0 ms
64 bytes from 192.168.2.2: icmp_seq=109 ttl=255 time=490.0 ms
64 bytes from 192.168.2.2: icmp_seq=110 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=111 ttl=255 time=0.0 ms
64 bytes from 192.168.2.2: icmp_seq=112 ttl=255 time=0.0 ms

--- 192.168.2.2 ping statistics ---
113 packets transmitted, 113 packets received, 0% packet loss
round-trip min/avg/max = 0.0/926.6/9140.1 ms

attached mail follows:

I'm using pre6-5 now and still having problems with severe lag pinging my
ethernet adres 192.168.2.2 or my real internet adres.
pinging localhost seems to ping fine.
is this a kernel bug or did i something wrong?

--- 192.168.2.2 ping statistics ---
113 packets transmitted, 113 packets received, 0% packet loss
round-trip min/avg/max = 0.0/926.6/9140.1 ms

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Borislav Deianov: "Re: SCHED_RR is broken + patch"
Previous message: Russell King: "Patch: busmouse.c - more doc and spinlock optimisation"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Apr 30 2000 - 21:00:10 EST