2.2.9 to 2.2.12-20 upgrade problem (fwd)

Eric Christian Berg ecb@ComptekAmherst.com
Fri Oct 22 18:43:35 1999


I've done a tulip-diag -m and got:

tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21143 Tulip adapter at 0xdc80.
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit threshold is 128.
  The NWay status register is 45e1d2cc.
   No MII transceivers found!
  Internal autonegotiation state is 'Negotiation complete'.

Just to add to the information below.

---------- Forwarded message ----------
Subject: 2.2.9 to 2.2.12-20 upgrade problem
From: Eric Christian Berg <ecb@amherst.com>
Date: Fri Oct 22 18:43:35 1999
To: Linux Tulip Bug Mailing List <linux-tulip-bug@beowulf.gsfc.nasa.gov>

I was previously running Red Hat 6.0 with a 2.2.9 kernel without a
problem. My output for eth0 detection was such:

Oct 11 16:40:22 samedi kernel: tulip.c:v0.89H 5/23/98
becker@cesdis.gsfc.nasa.gov
Oct 11 16:40:22 samedi kernel: eth0: Digital DS21142/3 Tulip at 0xdc80, 00
00 f8 1a 92 ff, IRQ 9. 
Oct 11 16:40:22 samedi kernel: eth0:  EEPROM default media type Autosense. 
Oct 11 16:40:22 samedi kernel: eth0:  Index #0 - Media 10baseT (#0)
described by a 21142 Serial PHY (2) block. 
Oct 11 16:40:22 samedi kernel: eth0:  Index #1 - Media 10baseT-FD (#4)
described by a 21142 Serial PHY (2) block. 
Oct 11 16:40:22 samedi kernel: eth0:  Index #2 - Media 100baseTx (#3)
described by a 21143 SYM PHY (4) block. 
Oct 11 16:40:22 samedi kernel: eth0:  Index #3 - Media 100baseTx-FD (#5)
described by a 21143 SYM PHY (4) block. 
Oct 11 16:40:17 samedi network: Bringing up interface eth0 succeeded

Last night I upgraded to Red Hat 6.1, which ships with the 2.2.12-20
kernel. The network install worked fine, but when I booted up I got:

Oct 11 18:27:34 samedi kernel: tulip.c:v0.89H 5/23/98
becker@cesdis.gsfc.nasa.gov
Oct 11 18:27:34 samedi kernel: eth0: Digital DS21142/3 Tulip at 0xdc80,
EEPROM not present, 00 4c 69 6e 75 79, IRQ 0. 
Oct 11 18:27:34 samedi kernel: eth0: Old style EEPROM -- no media
selection information. 

I attempted to resolve the problem by switching the driver back to the
version I had with 2.2.9 (the diffs showed a few minor changes) but got
the same result. So, I went to the site and got the newest driver and got
similar results:

Oct 12 13:23:27 samedi kernel: tulip.c:v0.91g 7/16/99
becker@cesdis.gsfc.nasa.gov
Oct 12 13:23:27 samedi kernel: eth0: Digital DS21143 Tulip rev 48 at
0xdc80, EEPROM not present, 00:4C:69:6E:75:79, IRQ 9. 
Oct 12 13:23:27 samedi kernel: eth0: Old style EEPROM with no media
selection information. 
Oct 12 13:23:27 samedi kernel: eth0: Tx hung, 9 vs. 0. 
Oct 12 13:23:27 samedi kernel: eth0: 21140 transmit timed out, status
0801fbff, SIA 7fffffff 00000001 7fffccff fcdb0008, resetting... 
Oct 12 13:23:33 samedi kernel: eth0: Tx hung, 9 vs. 0. 
Oct 12 13:23:33 samedi kernel: eth0: 21140 transmit timed out, status
0801fbff, SIA 7fffffff 00000001 7fffccff fcdb0008, resetting... 
Oct 12 13:23:45 samedi kernel: eth0: Tx hung, 15 vs. 0. 
Oct 12 13:23:45 samedi kernel: eth0: 21140 transmit timed out, status
0801fbff, SIA 7fffffff 00000001 7fffccff fcc00008, resetting... 

Note that I am able to boot to the old 2.2.9 kernel still without a
problem. I have also had Plug and Play turned off in the BIOS the whole
time. 

Any thoughts?

-- 
Eric Christian Berg
Asst System Administrator, Comptek Amherst Systems
(716) 631-0088 ext. 199
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GP/S d- s+:+ a- C++(+++)$ ULIOS++++$ P+++$ L+++ E--- W++ N+ o w--- M- V--
PS+ PE++ Y+ t+@ 5+ X- R++ tv+ b++ DI+ D--- G e+*>++++ h r++ y**
------END GEEK CODE BLOCK------