I have installed Linux in my HP KAYAK XA PC and have problems with sending ping continously from the PC. Ping stops after 10-20 pings. Ping can be "awakened" again by sending one ping from another PC towards the KAYAK PC. Pinging stops therafter again after 10-20 pings, can be "awak- ened" again and so on... The problem is the same for RedHat 7.1 and SuSE 7.3 installations. There is no problem sending pings continously when using Windows98. Presently I have SuSE 7.3 with kernel 2.4.10 installed. I have disabled all power management (apm) related functions in BIOS. lspci command responds with the circuit 79C970. dmsg output shows 79C971. I have tested IRQ number 3 and 11 for pcnet32 interrupt without any change in behavior. mii-tool command responds with: eth0: no autonegotiation, 10baseT-HD, link ok mii-diag command responds with: Using the default interface 'eth0'. Basic registers of MII PHY #1: 1000 782d 7810 0000 01e1 0021 0000 0000. Basic mode control register 0x1000: Auto-negotiation enabled. You have link beat, and everything is working OK. Your link partner is generating 10baseT link beat (no autonegotiation). Files from ping test from KAYAK PC (192.168.1.1) to other PC (192.168.1.3): Record from ping window of 192.168.1.1: kayak:~ # ping 192.168.1.3 PING lte5100.pikeperch (192.168.1.3) from 192.168.1.1 : 56(84) bytes of data. 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=1 ttl=255 time=1.118 msec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=2 ttl=255 time=1.055 msec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=3 ttl=255 time=4.109 msec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=4 ttl=255 time=1.025 msec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=5 ttl=255 time=20.628 msec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=6 ttl=255 time=878 usec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=7 ttl=255 time=927 usec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=8 ttl=255 time=880 usec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=9 ttl=255 time=2.429 msec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=10 ttl=255 time=898 usec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=11 ttl=255 time=2.321 msec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=12 ttl=255 time=876 usec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=13 ttl=255 time=988 usec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=14 ttl=255 time=891 usec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=15 ttl=255 time=902 usec 64 bytes from lte5100.pikeperch (192.168.1.3): icmp_seq=16 ttl=255 time=966 usec (* Here ping stopped and I interrupted pinging by pressing ctrl-C on the keyboard*) ping: sendmsg: Interrupted system call --- lte5100.pikeperch ping statistics --- 17 packets transmitted, 16 received, 5% loss, time 22152ms rtt min/avg/max/mdev = 0.876/2.555/20.628/4.744 ms Record from tcpdump in other window of 192.168.1.1: 15:56:10.048375 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:10.049327 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:11.050558 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:11.051509 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:12.060543 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:12.064563 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:13.070533 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:13.071476 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:14.080539 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:14.101081 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:15.045658 arp who-has 192.168.1.1 tell 192.168.1.3 15:56:15.045710 arp reply 192.168.1.1 is-at 0:60:b0:86:11:f5 15:56:15.090544 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:15.091334 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:16.100540 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:16.101381 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:17.110534 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:17.111331 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:18.120537 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:18.122882 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:19.130536 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:19.131353 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:20.140534 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:20.142776 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:21.150531 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:21.151329 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:22.160538 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:22.161446 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:23.170531 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:23.171344 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:24.180540 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:24.181359 192.168.1.3 > 192.168.1.1: icmp: echo reply 15:56:25.190534 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 15:56:25.191419 192.168.1.3 > 192.168.1.1: icmp: echo reply Record from tcpdump in window of 192.168.1.3 (ignore time stamp as I forgot to set the clock of this PC): 06:15:08.325007 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:08.325305 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:09.327154 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:09.327455 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:10.340201 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:10.340472 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:11.347042 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:11.347343 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:12.376632 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:12.376912 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:13.321461 arp who-has 192.168.1.1 tell 192.168.1.3 (0:a0:d1:1:54:18) 06:15:13.321973 arp reply 192.168.1.1 is-at 0:60:b0:86:11:f5 (0:a0:d1:1:54:18) 06:15:13.366868 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:13.367127 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:14.376833 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:14.377133 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:15.386784 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:15.387050 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:16.396837 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:16.397102 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:17.406710 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:17.406987 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:18.416676 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:18.418370 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:19.426629 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:19.426889 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:20.436692 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:20.436965 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:21.446561 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:21.446825 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:22.456531 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:22.456799 192.168.1.3 > 192.168.1.1: icmp: echo reply 06:15:23.466573 192.168.1.1 > 192.168.1.3: icmp: echo request (DF) 06:15:23.466824 192.168.1.3 > 192.168.1.1: icmp: echo reply Conclusion: 17 messages were sent to the ethernet interface board but only 16 appeared in the output from the board. For some reason the message is "swallowed" in the board. Does anyone have any clue on what is going on and/or any advices? Best regards Bengt T