Problem with 2.4.22 and SMC EtherPower II 9432

From: Adrian Bunk (bunk_at_fs.tum.de)
Date: 10/20/03

  • Next message: Paul Larson: "Re: RH7.3 can't compile 2.6.0-test8"
    Date:	Mon, 20 Oct 2003 22:59:33 +0200
    To: Donald Becker <becker@scyld.com>, linux-net@vger.kernel.org, jgarzik@pobox.com
    
    

    Hi,

    on two different machines the ethernet card works with kernel 2.2.20 but
    not with kernel 2.4.22 (both contain machines contain the same card).

    Card:

    lspci:
    00:0b.0 Ethernet controller: Standard Microsystems Corp [SMC] 83C170QF (rev 08)

    cat /proc/pci:
      Bus 0, device 11, function 0:
        Ethernet controller: SMC 9432 TX (rev 8).
          Fast devsel. Fast back-to-back capable. IRQ 10. Master Capable.
    Latency=32. Min Gnt=8.Max Lat=28.
          I/O at 0xb000 [0xb001].
          Non-prefetchable 32 bit memory at 0xde800000 [0xde800000].

    Kernel 2.2.20 (working):
    kernel: eth0: SMSC EPIC/100 83c170 at 0xb000, IRQ 10, 00:e0:29:3d:e4:6f.
    kernel: eth0: MII transceiver #3 control 3000 status 7809.
    kernel: eth0: Autonegotiation advertising 01e1 link partner 0001.
    ...
    kernel: eth0: Setting full-duplex based on MII #3 link partner capability of 45e1.

    kernel 2.4.22 (not working):
    kernel: epic100.c:v1.11 1/7/2001 Written by Donald Becker
    <becker@scyld.com>
    kernel: http://www.scyld.com/network/epic100.html
    kernel: (unofficial 2.4.x kernel port, version 1.11+LK1.1.14, Aug 4,
    2002)
    kernel: epic100(00:0b.0): MII transceiver #3 control 3000 status 7809.
    kernel: epic100(00:0b.0): Autonegotiation advertising 01e1 link partner
    0001.
    kernel: eth0: SMSC EPIC/100 83c170 at 0xb000, IRQ 10, 00:e0:29:3d:e4:6f.
    ...
    kernel: eth0: Setting full-duplex based on MII #3 link partner capability of 45e1.
    kernel: NETDEV WATCHDOG: eth0: transmit timed out
    kernel: eth0: Transmit timeout using MII device, Tx status 4003.
    kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 2/12.
    kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
    kernel: eth0: Setting half-duplex based on MII #3 link partner
    capability of 0001.
    kernel: NETDEV WATCHDOG: eth0: transmit timed out
    kernel: eth0: Transmit timeout using MII device, Tx status 0003.
    kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 3/12.
    kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
    kernel: NETDEV WATCHDOG: eth0: transmit timed out
    kernel: eth0: Transmit timeout using MII device, Tx status 000b.
    kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 4/12.
    kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
    kernel: NETDEV WATCHDOG: eth0: transmit timed out
    kernel: eth0: Transmit timeout using MII device, Tx status 000b.
    kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 5/12.
    kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
    kernel: NETDEV WATCHDOG: eth0: transmit timed out
    kernel: eth0: Transmit timeout using MII device, Tx status 000b.
    kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 6/12.
    kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
    kernel: eth0: Too much work at interrupt, IntrStatus=0x008d0004.
    kernel: NETDEV WATCHDOG: eth0: transmit timed out
    kernel: eth0: Transmit timeout using MII device, Tx status 000b.
    kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 7/17.
    kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.

    Does anyone have an idea what's going wrong in 2.4.22?

    TIA
    Adrian

    -- 
           "Is there not promise of rain?" Ling Tan asked suddenly out
            of the darkness. There had been need of rain for many days.
           "Only a promise," Lao Er said.
                                           Pearl S. Buck - Dragon Seed
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Paul Larson: "Re: RH7.3 can't compile 2.6.0-test8"

    Relevant Pages

    • 2.6.0-test problems loading network drivers
      ... with some kernel hacking options. ... the pcmcia network drivers (SMC 2632W wireless ethernet card). ... PCI: Assigned IRQ 9 for device 00:0a.0 ... eth0: Station identity 001f:0003:0000:0008 ...
      (Linux-Kernel)
    • ethernet not working (FC4)
      ... I just updated my laptop from Fedora Core 3 (kernel 2.6.9-1.667) ... Now eth0 (ethernet) does not correctly work, although it did work with FC3. ...
      (Fedora)
    • Re: renaming kernel devices [was: VIA EPIA EK: strange eth dev numbering]
      ... There never *were* days when eth0 remained eth0 across such changes. ... Shuffling rest of the interfaces if eth0 is removed and no this persistent ... There are PCI wireless cards, ... but during kernel lifetime it ...
      (Linux-Kernel)
    • Intel Gigabit NIC (2.6.5 -> 2.6.10) Bug(?) Found
      ... Something in the kernel changed regarding the Intel e1000 driver from ... Normally, I never really looked at my ifconfig eth0, eth1 etc because I ... with GigE nics, on one there are very few if any errors on the nic ... ethtool and installed it and did a basic query for network setting ...
      (Linux-Kernel)
    • ADSL problems
      ... Kernel 2.4.20 ... iface eth0 inet dhcp ... The dhclient config file is empty, so far, but judging from ... all outgoing traffic fails immediately (i.e. it doesn't time out, ...
      (comp.os.linux.networking)