Re: [parisc-linux] quad tulip now not functional in 2.4.20

[grundler@dsl2.external.hp.com (Grant Grundler)]

On Sun, Dec 15, 2002 at 11:45:12PM -0700, Ed Schaller wrote:
> I have a B180 that I have been using as a firewall/router for some time
> now. Along with the built in tulip ethernet card, I also have a Adaptec
> quad ethernet card that is also tulip based. This has worked fine in
> 2.4.17-2.4.19 but no longer works in 2.4.20-pa13. Although I can
> ifconfig up the interfaces, no traffic goes through and mii-tool reports
> that the interfaces do not exist (except for the built in one).

I've looked a bit at the same problem on A500 with
a regular (single port) HP tulip card.

> In the following dmesg out takes for 2.4.20-pa13 and 2.4.19-32 (debian),
> it seems that the older kernel is finding the transceiver and
> successfully auto-negotiating the link while the newer is not.

yeah - same symptom that I saw.

> Any ideas how to solve this? Any help would be greatly appreciated.

I suspect it's a tulip driver bug.
I haven't had a chance to diff the 2.4.19 vs 2.4.20 tulip driver.
One idea might be to "forward port" the 2.4.19 drivers/net/tulip code
into 2.4.20.

thanks for the report,
grant

> Linux version 2.4.20-pa13 (root@landmine) (gcc version 3.0.4) #3 Tue Dec 10 01:35:34 MST 2002
> ...
> Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
> tulip0: no phy info, aborting mtable build
> tulip0:  MII transceiver #1 config 1000 status 782d advertising 01e1.
> eth0: Digital DS21143 Tulip rev 48 at 0xf0fff000, 00:60:B0:C4:5E:7B, IRQ 96.
> eth1: Digital DS21140 Tulip rev 34 at 0xf0efc000, 00:00:D1:1B:C8:90, IRQ 98.
> eth2: Digital DS21140 Tulip rev 34 at 0xf0efd000, 00:00:D1:1B:C8:B5, IRQ 99.
> eth3: Digital DS21140 Tulip rev 34 at 0xf0efe000, 00:00:D1:1B:C8:95, IRQ 96.
> eth4: Digital DS21140 Tulip rev 34 at 0xf0eff000, 00:00:D1:1B:70:33, IRQ 97.
> ...until ifconfig eth0-eth4
> eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
> 
> Linux version 2.4.19-32 (root@j5k) (gcc version 3.0.4) #1 Fri Nov 22 23:27:00 MST 2002
> ...
> Linux Tulip driver version 0.9.15-pre11 (May 11, 2002)
> tulip0: no phy info, aborting mtable build
> tulip0:  MII transceiver #1 config 1000 status 782d advertising 01e1.
> eth0: Digital DS21143 Tulip rev 48 at 0xff00, 00:60:B0:C4:5E:7B, IRQ 96.
> tulip1:  EEPROM default media type Autosense.
> tulip1:  Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
> tulip1:  MII transceiver #1 config 3100 status 7849 advertising 01e1.
> eth1: Digital DS21140 Tulip rev 34 at 0xec00, 00:00:D1:1B:C8:90, IRQ 98.
> tulip2:  EEPROM default media type Autosense.
> tulip2:  Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
> tulip2:  MII transceiver #1 config 3100 status 7849 advertising 01e1.
> eth2: Digital DS21140 Tulip rev 34 at 0xed00, 00:00:D1:1B:C8:B5, IRQ 99.
> tulip3:  EEPROM default media type Autosense.
> tulip3:  Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
> tulip3:  MII transceiver #1 config 3100 status 7849 advertising 01e1.
> eth3: Digital DS21140 Tulip rev 34 at 0xee00, 00:00:D1:1B:C8:95, IRQ 96.
> tulip4:  EEPROM default media type Autosense.
> tulip4:  Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
> tulip4:  MII transceiver #1 config 3100 status 7849 advertising 01e1.
> eth4: Digital DS21140 Tulip rev 34 at 0xef00, 00:00:D1:1B:70:33, IRQ 97.
> ...until ifconfig eth0-eth4
> eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
> eth1: Setting full-duplex based on MII#1 link partner capability of 45e1.
> eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
> eth3: Setting full-duplex based on MII#1 link partner capability of 41e1.
> eth4: Setting full-duplex based on MII#1 link partner capability of 41e1.
> 
> >>>------>
> 
> --
> 
> +-------------+-----------------------+---------------+
> | Ed Schaller | Dark Mist Networking  | psuedoshroom  |
> +-------------+-----------------------+---------------+