Linux-kernel mailing list archive 2000-23,: 3C59x Problem in 2.2.16

# 3C59x Problem in 2.2.16

Robert A. Morris (ramorris@dilithium.net)
Sat, 10 Jun 2000 00:25:28 -0400

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Chip Salzenberg: "Present Evidence Or Lay Off Red Hat (was Re: reiserfs)"
- Previous message: Anthony Barbachan: "Re: Floppy handling"
- Next in thread: Alan Cox: "Re: 3C59x Problem in 2.2.16"
- Reply: Alan Cox: "Re: 3C59x Problem in 2.2.16"

Hi,

I'm running a recently-compiled 2.2.16 final kernel, using distribution RedHat
6.2, and I'm seeing seemingly random problems with my ethernet connection,
using a 3Com 3C905B Cyclone (3Com's Fast EtherLink XL 10/100/BNC/AUI network
card). It doesn't seem to be a network problem - I have one other machine
running 2.2.15 with the same type of card, and there are no problems. Has
anyone else seen this? Is there a fix?

Randomly, web pages will fail to load, connections will time out, and so forth.
The most noticeable symptoms are printed below:

[root@DILITHIUM ramorris]# nslookup www.kernelnotes.org
*** Can't find server name for address 18.70.0.160: No response from server
*** Can't find server name for address 18.71.0.151: No response from server
*** Can't find server name for address 18.72.0.3: No response from server
*** Default servers are not available

And sometimes, randomly:

[root@DILITHIUM ramorris]# nslookup www.kernelnotes.org
*** Can't find server name for address 18.70.0.160: No response from server
*** Can't find server name for address 18.71.0.151: Timed out
*** Can't find server name for address 18.72.0.3: Timed out
*** Default servers are not available

Also, I sometimes get ping results like the following:

[root@DILITHIUM ramorris]# ping search.yahoo.com
PING search.yahoo.com (204.71.200.99) from 18.244.1.45 : 56(84) bytes of data.
64 bytes from 169.254.122.98: icmp_seq=0 ttl=128 time=1.0 ms
64 bytes from 204.71.200.99: icmp_seq=0 ttl=242 time=76.7 ms (DUP!)
64 bytes from 169.254.122.98: icmp_seq=1 ttl=128 time=0.4 ms
64 bytes from s01.yahoo.com (204.71.200.99): icmp_seq=1 ttl=242 time=74.0 ms (DUP!)
64 bytes from 169.254.122.98: icmp_seq=2 ttl=128 time=0.3 ms
64 bytes from s01.yahoo.com (204.71.200.99): icmp_seq=2 ttl=242 time=75.1 ms (DUP!)
64 bytes from 169.254.122.98: icmp_seq=3 ttl=128 time=0.3 ms
64 bytes from s01.yahoo.com (204.71.200.99): icmp_seq=3 ttl=242 time=75.1 ms (DUP!)

--- search.yahoo.com ping statistics ---
4 packets transmitted, 4 packets received, +4 duplicates, 0% packet loss
round-trip min/avg/max = 0.3/37.8/76.7 ms

Notice the incorrect 169.254.122.98 address in the ping result - ping seems to
print this exact IP address no matter what host I try to ping.

One or more of these problems will occur several times if the commands are
repeated, then within 30 seconds to one minute they will disappear. The
problem did not occur with 2.2.15 or anything before, and seems to get worse
the longer the system is up (I don't notice the problem within a few hours after
rebooting).

I have also noticed that my dmesg log is full of line after line of:

eth0: Transmit error, Tx status register 82.

And ifconfig reports lots of network errors:

eth0 Link encap:Ethernet HWaddr 00:50:DA:6A:BE:C4
inet addr:18.244.1.45 Bcast:18.244.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:339995 errors:2873 dropped:0 overruns:0 frame:5637
TX packets:45916 errors:0 dropped:0 overruns:0 carrier:45921
collisions:2780 txqueuelen:100
Interrupt:11 Base address:0x9400

dmesg reports the following information on my ethernet card:

3c59x.c:v0.99H 27May00 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
eth0: 3Com 3c905B Cyclone 10/100/BNC at 0x9400, 00:50:da:6a:be:c4, IRQ 11
8K byte-wide RAM 5:3 Rx:Tx split, 10Mbs AUI interface.
Enabling bus-master transmits and whole-frame receives.

And finally, the kernel info;

[root@DILITHIUM ramorris]# uname -a
Linux DILITHIUM.MIT.EDU 2.2.16 #1 Wed Jun 7 20:05:34 EDT 2000 i686 unknown

CPU is an Athlon 800, mainboard is an Asus K7V (VIA KX133) with the latest BIOS.

-
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: Chip Salzenberg: "Present Evidence Or Lay Off Red Hat (was Re: reiserfs)"
- Previous message: Anthony Barbachan: "Re: Floppy handling"
- Next in thread: Alan Cox: "Re: 3C59x Problem in 2.2.16"
- Reply: Alan Cox: "Re: 3C59x Problem in 2.2.16"