Re: 3C59x Problem in 2.2.16

From: Andrew Morton (andrewm@uow.edu.au)
Date: Sat Jun 10 2000 - 22:47:26 EDT

  • Next message: Hans Reiser: "Re: (reiserfs) Re: New Linux 2.5 - 2.6 TODO (Alan Cox suggestsdelaying"

    "Robert A. Morris" wrote:
    >
    > ...
    > I have also noticed that my dmesg log is full of line after line of:
    >
    > eth0: Transmit error, Tx status register 82.

    A transmit reclaim error. This means that someone has caused a
    collision after the NIC has transmitted more than 128 bytes of a
    particular frame.

    > 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

    Ouch.

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

    Are you really, really sure that there isn't something on the network
    which is erroneously operating in full duplex mode? According to
    http://www.scyld.com/network/vortex.html, a reclaim ("out of window")
    error is due to a network problem.

    You're on a half-duplex LAN, right? 10 or 100 mbit? Are you using the
    BNC or AUI interfaces? Are there many other hosts on that LAN?

    It is possible that the driver is deciding to start operating with the
    wrong media interface or duplex, but it's hard to explain how this could
    cause such very late collisions.

    As a last resort, if you're sure it's not a LAN prob could you please
    try forcing the driver into the correct media settings with
    'options=0xNN' and perhaps 'full_duplex=1' as per the instructions at
    http://www.scyld.com/network/vortex.html?

    Thanks.

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



    This archive was generated by hypermail 2b29 : Sat Jun 10 2000 - 22:46:26 EDT