From: "Andreas K. Huettel" <Andreas.Huettel@Physik.Uni-Muenchen.DE>
To: linux-kernel@vger.kernel.org
Subject: 2.4.5-ac14: machine responds to _every fifth_ ping!
Date: Sat, 16 Jun 2001 23:09:56 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0106162241540.27001-200000@ankogel.cip.physik.uni-muenchen.de> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2340 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear all,
I am using a box with 2.4.5-ac14, 3c59x eth0 driver, 3c905C network card.
When working with it, the network has been behaving ok. Now I ping it from
a remote location, and I see the following strange effect:
After a few seconds, only every fifth ping gets back! (quite
exactly, reproducible). Ping output attached.
Another box on the same hub responds totally normal, so it is no network
congestion. I cannot ssh in at the moment, unfortunately. I tried several
different ping source machines, running 2.2.14(SuSE71), 2.2.14 SMP
(vanilla+int.crypto), 2.2.19, and a SPARCstation - they all give basically
the same result.
(Well, besides the target machine is one of these still constantly logging
"clock timer configuration lost - probably a VIA686a motherboard".)
lspci:
00:00.0 Host bridge: Acer Laboratories Inc. [ALi]: Unknown device 1647
(rev 04)
00:01.0 PCI bridge: Acer Laboratories Inc. [ALi] M5247
00:02.0 USB Controller: Acer Laboratories Inc. [ALi] M5237 USB (rev 03)
00:04.0 IDE interface: Acer Laboratories Inc. [ALi] M5229 IDE (rev c4)
00:05.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev
10)
00:06.0 USB Controller: Acer Laboratories Inc. [ALi] M5237 USB (rev 03)
00:07.0 ISA bridge: Acer Laboratories Inc. [ALi] M1533 PCI to ISA Bridge
[Aladdin IV]
00:0b.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink]
(rev 74)
00:11.0 Bridge: Acer Laboratories Inc. [ALi] M7101 PMU
01:00.0 VGA compatible controller: nVidia Corporation NV11 (rev a1)
I hope this helps fixing some bug.
best regards, Andreas
- ---------------------------------------------------------------------
Andreas K. Huettel andreas@akhuettel.de
81627 Muenchen huettel@qubit.org
Germany http://www.akhuettel.de/
- ---------------------------------------------------------------------
Please use GNUPG or PGP for signed and encrypted email. My public key
can be found at http://www.akhuettel.de/pgp_key.html
- ---------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7K8spL+gLs3iH94cRAisYAKCBS4t4zpO3Pro6fUPirHnJzWF84QCeI/ok
QSZa20+XBuESVEf+KqHEvlA=
=AkrB
-----END PGP SIGNATURE-----
[-- Attachment #2: Type: TEXT/PLAIN, Size: 5295 bytes --]
huettel@centralservices:~/DiplomTalk > ping qubit
PING qubit.some-domain (x.y.142.6): 56 data bytes
64 bytes from x.y.142.6: icmp_seq=0 ttl=255 time=0.587 ms
64 bytes from x.y.142.6: icmp_seq=1 ttl=255 time=0.545 ms
64 bytes from x.y.142.6: icmp_seq=2 ttl=255 time=0.551 ms
64 bytes from x.y.142.6: icmp_seq=3 ttl=255 time=0.544 ms
64 bytes from x.y.142.6: icmp_seq=4 ttl=255 time=0.545 ms
64 bytes from x.y.142.6: icmp_seq=9 ttl=255 time=0.547 ms
64 bytes from x.y.142.6: icmp_seq=14 ttl=255 time=0.544 ms
64 bytes from x.y.142.6: icmp_seq=19 ttl=255 time=0.553 ms
64 bytes from x.y.142.6: icmp_seq=24 ttl=255 time=0.538 ms
64 bytes from x.y.142.6: icmp_seq=29 ttl=255 time=0.528 ms
64 bytes from x.y.142.6: icmp_seq=34 ttl=255 time=0.545 ms
64 bytes from x.y.142.6: icmp_seq=39 ttl=255 time=0.545 ms
64 bytes from x.y.142.6: icmp_seq=44 ttl=255 time=0.542 ms
64 bytes from x.y.142.6: icmp_seq=49 ttl=255 time=0.522 ms
64 bytes from x.y.142.6: icmp_seq=54 ttl=255 time=0.519 ms
64 bytes from x.y.142.6: icmp_seq=59 ttl=255 time=0.535 ms
64 bytes from x.y.142.6: icmp_seq=64 ttl=255 time=0.540 ms
--- qubit.some-domain ping statistics ---
65 packets transmitted, 17 packets received, 73% packet loss
round-trip min/avg/max = 0.519/0.542/0.587 ms
huettel@centralservices:~/DiplomTalk > ping qubit
PING qubit.some-domain (x.y.142.6): 56 data bytes
64 bytes from x.y.142.6: icmp_seq=0 ttl=255 time=0.607 ms
64 bytes from x.y.142.6: icmp_seq=1 ttl=255 time=0.545 ms
64 bytes from x.y.142.6: icmp_seq=2 ttl=255 time=0.540 ms
64 bytes from x.y.142.6: icmp_seq=3 ttl=255 time=0.537 ms
64 bytes from x.y.142.6: icmp_seq=4 ttl=255 time=0.539 ms
64 bytes from x.y.142.6: icmp_seq=5 ttl=255 time=0.537 ms
64 bytes from x.y.142.6: icmp_seq=6 ttl=255 time=0.538 ms
64 bytes from x.y.142.6: icmp_seq=11 ttl=255 time=0.543 ms
64 bytes from x.y.142.6: icmp_seq=16 ttl=255 time=0.550 ms
64 bytes from x.y.142.6: icmp_seq=21 ttl=255 time=0.518 ms
64 bytes from x.y.142.6: icmp_seq=26 ttl=255 time=0.609 ms
64 bytes from x.y.142.6: icmp_seq=31 ttl=255 time=0.543 ms
64 bytes from x.y.142.6: icmp_seq=36 ttl=255 time=0.545 ms
64 bytes from x.y.142.6: icmp_seq=41 ttl=255 time=0.551 ms
64 bytes from x.y.142.6: icmp_seq=46 ttl=255 time=0.543 ms
64 bytes from x.y.142.6: icmp_seq=51 ttl=255 time=0.537 ms
--- qubit.some-domain ping statistics ---
52 packets transmitted, 16 packets received, 69% packet loss
round-trip min/avg/max = 0.518/0.548/0.609 ms
huettel@centralservices:~/DiplomTalk > ping qubit
PING qubit.some-domain (x.y.142.6): 56 data bytes
64 bytes from x.y.142.6: icmp_seq=0 ttl=255 time=0.598 ms
64 bytes from x.y.142.6: icmp_seq=1 ttl=255 time=0.550 ms
64 bytes from x.y.142.6: icmp_seq=2 ttl=255 time=0.550 ms
64 bytes from x.y.142.6: icmp_seq=3 ttl=255 time=0.545 ms
64 bytes from x.y.142.6: icmp_seq=4 ttl=255 time=0.547 ms
64 bytes from x.y.142.6: icmp_seq=5 ttl=255 time=0.520 ms
64 bytes from x.y.142.6: icmp_seq=6 ttl=255 time=0.543 ms
64 bytes from x.y.142.6: icmp_seq=10 ttl=255 time=0.610 ms
64 bytes from x.y.142.6: icmp_seq=15 ttl=255 time=0.549 ms
64 bytes from x.y.142.6: icmp_seq=20 ttl=255 time=0.545 ms
64 bytes from x.y.142.6: icmp_seq=25 ttl=255 time=0.544 ms
64 bytes from x.y.142.6: icmp_seq=30 ttl=255 time=0.554 ms
64 bytes from x.y.142.6: icmp_seq=35 ttl=255 time=0.542 ms
64 bytes from x.y.142.6: icmp_seq=40 ttl=255 time=0.554 ms
64 bytes from x.y.142.6: icmp_seq=46 ttl=255 time=0.548 ms
64 bytes from x.y.142.6: icmp_seq=51 ttl=255 time=0.515 ms
64 bytes from x.y.142.6: icmp_seq=56 ttl=255 time=0.547 ms
64 bytes from x.y.142.6: icmp_seq=61 ttl=255 time=0.551 ms
--- qubit.some-domain ping statistics ---
63 packets transmitted, 18 packets received, 71% packet loss
round-trip min/avg/max = 0.515/0.550/0.610 ms
huettel@centralservices:~/DiplomTalk > ping qubit
PING qubit.some-domain (x.y.142.6): 56 data bytes
64 bytes from x.y.142.6: icmp_seq=0 ttl=255 time=0.595 ms
64 bytes from x.y.142.6: icmp_seq=1 ttl=255 time=0.553 ms
64 bytes from x.y.142.6: icmp_seq=2 ttl=255 time=0.556 ms
64 bytes from x.y.142.6: icmp_seq=3 ttl=255 time=0.555 ms
64 bytes from x.y.142.6: icmp_seq=4 ttl=255 time=0.549 ms
64 bytes from x.y.142.6: icmp_seq=5 ttl=255 time=0.520 ms
64 bytes from x.y.142.6: icmp_seq=6 ttl=255 time=0.549 ms
64 bytes from x.y.142.6: icmp_seq=10 ttl=255 time=0.533 ms
64 bytes from x.y.142.6: icmp_seq=15 ttl=255 time=0.538 ms
64 bytes from x.y.142.6: icmp_seq=20 ttl=255 time=0.566 ms
64 bytes from x.y.142.6: icmp_seq=25 ttl=255 time=0.548 ms
64 bytes from x.y.142.6: icmp_seq=30 ttl=255 time=0.550 ms
64 bytes from x.y.142.6: icmp_seq=35 ttl=255 time=0.547 ms
64 bytes from x.y.142.6: icmp_seq=41 ttl=255 time=0.534 ms
64 bytes from x.y.142.6: icmp_seq=46 ttl=255 time=0.529 ms
64 bytes from x.y.142.6: icmp_seq=51 ttl=255 time=0.556 ms
64 bytes from x.y.142.6: icmp_seq=56 ttl=255 time=0.525 ms
64 bytes from x.y.142.6: icmp_seq=61 ttl=255 time=0.609 ms
64 bytes from x.y.142.6: icmp_seq=66 ttl=255 time=0.545 ms
64 bytes from x.y.142.6: icmp_seq=71 ttl=255 time=0.542 ms
--- qubit.some-domain ping statistics ---
73 packets transmitted, 20 packets received, 72% packet loss
round-trip min/avg/max = 0.520/0.549/0.609 ms
huettel@centralservices:~/DiplomTalk >
reply other threads:[~2001-06-16 21:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.21.0106162241540.27001-200000@ankogel.cip.physik.uni-muenchen.de \
--to=andreas.huettel@physik.uni-muenchen.de \
--cc=andreas@akhuettel.de \
--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;
as well as URLs for NNTP newsgroup(s).