[epic] epic100, kernel 2.4.18 -- timeout,

Alexis Zubrow azubrow@galton.uchicago.edu
Thu Mar 28 20:38:00 2002


hi.

I'm a relative newbie to linux.  I was using the epic100 for a
smc9432btx card under the 2.4.17 kernel.  Everything was fine.  I upgraded
to the 2.4.18 and I seem to be having problems with getting my card to
work. I've consulted what documentation I could find, the mailing
lists, and a diagnostic program (epic-diag).  Despite this, I haven't
had a ton of luck figuring out why the card seems to  be continuously
timing out every time it tries to make a connection.

I've tried a bunch of diagnostics and triple checked my configuration, but
I'm not sure where to go from here.  Any suggestions on how to tweek
either the start up configuration or the driver?

Thanks in advance,
Alexis


What follows is some configuration info, error messages, and diagnostics:

Configuration--
built 2.4.18 kernel for SMP, epic100 tested as module and as part of
kernel.


Error Messages (from dmesg)--

epic100(00:0c.0): MII transceiver #3 control 3400 status 7849.
epic100(00:0c.0): Autonegotiation advertising 01e1 link partner 0001.
eth0: SMSC EPIC/100 83c170 at 0x1400, IRQ 5, 00:04:e2:09:cb:64.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout using MII device, Tx status 0003.
eth0: Restarting the EPIC chip, Rx 0/0 Tx 0/10.
eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
NETDEV WATCHDOG: eth0: transmit timed out
(this pattern repeats ad infinitum)

Diagnostics -- using epic-diag
ndex #1: Found a SMSC EPIC/100 83c170 adapter at 0x1400.
The EPIC/100 chip appears to be active, so some registers will not be
read.
To see all register values use the '-f' flag.
 No interrupt sources are pending.
 Rx state is 'Running', Tx state is 'Running'.
  Transmitter: slot time 512 bits, half-duplex mode.
  Last transmit OK, 0 collisions.
  Receiver control is 3769000c, multicast mode.
  The last Rx frame was 0 bytes, status 0.
 MII PHY found at address 3.
 MII PHY #3 transceiver registers:
   3000 7849 0022 561b 01e1 0001 0004 2001
   ffff ffff ffff ffff ffff ffff ffff ffff
   01c0 0000 8010 8020 4f02 0304 0026 0000
   0000 c1bf 0000 ffff ffff ffff ffff ffff.
 MII PHY #3 transceiver registers:
   3000 7849 0022 561b 01e1 0001 0004 2001
   ffff ffff ffff ffff ffff ffff ffff ffff
   01c0 0000 d011 8020 4f52 0304 0026 0000
   0000 c1bf 0000 ffff ffff ffff ffff ffff.
 Basic mode control register 0x3000: Auto-negotiation enabled.
 Basic mode status register 0x7849 ... 7849.
   Link status: not established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
 Vendor ID is 00:08:95:--:--:--, model 33 rev. 11.
   Vendor/Part: AdHoc Technology AH101LF.
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0001:.
   Negotiation did not complete.
  TDK format vendor-specific registers 16..18 are 0x01c0 0x0000 0xd011
      Link polarity is detected as normal.
      Auto-negotiation had no common media, 10Mbps half duplex.
      Rx link in fail state, PLL locked.
      No new link status events.