[tulip-bug] oddities with tulip.c (v0.92 4/17/2000) & compile problems

Mon, 27 Nov 2000 11:47:23 -0500

Greetings.  I'm new to the list :)

I've been using version 2.0 of the Linksys EtherFast 10/100 board along
with the v0.92 tulip driver in Linux for many moons without a problem. 
That is until last night.

I recently upgraded my home machine from a pIII 500 to a Thunderbird
1000.  The upgrade was done last Wednesday evening (*not* last night
when the problems occured).  Everything in the new box, with the
exception of the mainboard, CPU and RAM, is identical to the old setup
which worked flawlessly.  The kernel is 2.2.17 and out of nowhere last
night the network vanished.

I thought the culprit was my masq box but probing through syslog files
on the downed machine I came across the following:

Nov 26 21:05:10 behemoth kernel: eth0: Restarted Rx at 388699 / 388699.
Nov 26 21:05:10 behemoth last message repeated 80 times
Nov 26 21:05:12 behemoth kernel: 99.
Nov 26 21:05:12 behemoth kernel: eth0: Restarted Rx at 388699 / 388699.
Nov 26 21:05:12 behemoth last message repeated 389 times
Nov 26 21:05:25 behemoth kernel: eth0: Transmit timed out, status
ffffffff, CSR12 4081d0cc, resetting...
Nov 26 21:06:00 behemoth last message repeated 7 times
Nov 26 21:07:00 behemoth last message repeated 12 times
Nov 26 21:08:00 behemoth last message repeated 12 times
Nov 26 21:09:00 behemoth last message repeated 12 times
Nov 26 21:10:00 behemoth last message repeated 12 times
Nov 26 21:11:00 behemoth last message repeated 12 times
Nov 26 21:11:10 behemoth last message repeated 2 times
Nov 26 21:11:10 behemoth login: pam_unix session started for user root,
service login 
Nov 26 21:11:15 behemoth kernel: eth0: Transmit timed out, status
ffffffff, CSR12 4081d0cc, resetting...
Nov 26 21:11:20 behemoth kernel: eth0: Transmit timed out, status
ffffffff, CSR12 4081d0cc, resetting...

I'm not much of a hardware guy; can anyone else make sense of this?

Unfortunately I did not have a copy of tulip-diag at the time of the
downtime.  Output of tulip-diag -f -aa -ee at the time of this email,
though, is:

tulip-diag.c:v2.04 9/26/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Lite-On PNIC-II adapter at 0xe000.
Lite-On PNIC-II chip registers at 0xe000:
  fff88000 ffffffff ffffffff 0f9d4800 0f9d4a00 e4660000 01002002
effffbff
  fffe0000 00fecf00 ffffffff fffe0000 40a1d0cc ffff0000 ffffffff
fff00000
  03300000 03300000 03300000 f40fffe0 2000427f 00001140 e3cc548f
a000a000
  e3cc548f 00000000 00000000 00000000 00000000 00000000 00000000
00000000
 Port selection is 10mpbs-serial, half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit threshold is 72.
  The NWay status register is 40a1d0cc.
 The current PNIC-II MAC address is 00:a0:cc:e3:8f:54 (a000a000
e3cc548f).
 The current PNIC-II WOL address is 00:a0:cc:e3:8f:54.
EEPROM size is 6.
  Ethernet MAC Station Address 00:a0:cc:e3:8f:54.
  Wake-On-LAN ID bytes a0:00:e3:cc:54:8f.
  PCI Subsystem IDs  Vendor 11ad Device 01c0
EEPROM contents:
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 a000 e3cc 548f a000 e3cc 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 548f 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 c001 11ad 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0014 0000 0000 2800 0000 c115 11ad 5f64
 ID block CRC 0xe3 (vs. 00).
  Full contents CRC 0x5f64 (read as 0x5f64).
  Internal autonegotiation state is 'Negotiation complete'.

I couldn't get the network card back up without a reboot.  I tried
removing the module and re-inserting it but this didn't work; I got a
"device is busy" error.  :/

In any case, after the reboot everything seemed fine once again (*knocks
on wood*).  Although now I'm testing out the ``v0.92n 11/3/2000'' tulip
driver.

On a different note, why doesn't the tulip driver compile with gcc
v2.95.2 under Linux?  Neither tulip.c nor pci-scan.c (any recent version
I could find) will build with this version of gcc; it generates a slew
of errors, much too many to list here.  I've tried on two different
linux boxes (SuSE 6.2 and SuSE 6.4).  Both the tulip.c and pci-scan.c,
however, (seemingly) build find with gcc 2.91.66.

Thanks for any help.

kw
--
Keith Warno                        keith.warno@valaran.com
Valaran Corporation Penguin Guy    http://www.valaran.com/