NIC on 2.4.19 SMP

NIC on 2.4.19 SMP

[Paul Hernandez]

Hello,

It was suggested to me that I forward this issue to you both.

OS:                                   2.4.19.SuSE  SMP
Motherboard:                    Intel Dual P4 Xeon Server board SE7500CW2
(latest bios off Intel site)
On-borad LAN controller:  Intel 82557/8/9 [Ether Pro 100] (rev 0d)
Addional NIC's tried:        3-COM 3C-905C-TX-M, Netgear FA311

dmesg output:

e100: eth0: Intel(R) 8255x-based Ethernet Adapter
   Mem:0xfc221000  IRQ:7  Speed:0 Mbps   Dx:N/A
   Failed to detect cable link
   Speed and duplex will be determined at time of connection
   Hardware receive checksums enabled
   cpu cycle saver enabled

All three NIC's worked fine on 2.4.18.SuSE (SuSE 8.0) however I
had to upgrade to correct non-functioning DMA on the on-board
ide controller which now works. (The on-board Promise FastTrack100
RAID controller which also worked on 2.4.18.SuSE now fails with
many "lost interrupts" messages...sigh)

Trying to debug using mii-tool of mii-diag yields:

SIOCGMIIPHY on eth0 failed:
Operation not supported
no MII interfaces found

ifconfig eth0 shows all is fine however cannot ping the gateway with 2.4.19
as can with 2.4.18. I can ping its own ip address fine,

Thanks in advance for any tips.

                                                Paul Hernandez  408-374-8686
x202
                                                Campbell, CA

Re: NIC on 2.4.19 SMP

[Felipe W Damasio]

On Fri, 2002-10-18 at 16:57, Paul Hernandez wrote:
> Hello,
> 
> It was suggested to me that I forward this issue to you both.
> 
> OS:                                   2.4.19.SuSE  SMP
> Motherboard:                    Intel Dual P4 Xeon Server board SE7500CW2
> (latest bios off Intel site)
> On-borad LAN controller:  Intel 82557/8/9 [Ether Pro 100] (rev 0d)
> Addional NIC's tried:        3-COM 3C-905C-TX-M, Netgear FA311
> 
> dmesg output:
> 
> e100: eth0: Intel(R) 8255x-based Ethernet Adapter

> SIOCGMIIPHY on eth0 failed:
> Operation not supported
> no MII interfaces found

	Try using the eepro100.c driver from the kernel, and not the one from
Intel (the driver from the kernel supports SIOCGMIIPHY).

	Though it does not seem a problem with the driver, you should try using
the one from the kernel and see if it helps.

	If it doesn't, reply this mail with the mii-diag output (and driver
version).

Felipe

Re: NIC on 2.4.19 SMP

[Jeff Garzik]

Felipe W Damasio wrote:
> On Fri, 2002-10-18 at 16:57, Paul Hernandez wrote:
> 
>>Hello,
>>
>>It was suggested to me that I forward this issue to you both.
>>
>>OS:                                   2.4.19.SuSE  SMP
>>Motherboard:                    Intel Dual P4 Xeon Server board SE7500CW2
>>(latest bios off Intel site)
>>On-borad LAN controller:  Intel 82557/8/9 [Ether Pro 100] (rev 0d)
>>Addional NIC's tried:        3-COM 3C-905C-TX-M, Netgear FA311
>>
>>dmesg output:
>>
>>e100: eth0: Intel(R) 8255x-based Ethernet Adapter
> 
> 
>>SIOCGMIIPHY on eth0 failed:
>>Operation not supported
>>no MII interfaces found
> 
> 
> 	Try using the eepro100.c driver from the kernel, and not the one from
> Intel (the driver from the kernel supports SIOCGMIIPHY).
> 
> 	Though it does not seem a problem with the driver, you should try using
> the one from the kernel and see if it helps.


I agree that comparison is useful, though it should be pointed out that 
ethtool is preferred for e100...

	Jeff

RE: NIC on 2.4.19 SMP

[Paul Hernandez]

Jeff and Felipe,

I naturally tried the default e100 first when I
installed SuSE 8.1 and only tried the eepro100.c
when the e100 failed identically. The e100 is harder
to debug w/o MII so felt the e100pro with MII might
shed some light.

Any suggestions. I'll happily assist in resolving this.

				Paul Hernandez  408-374-8686 x202
				Campbell, CA

-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Saturday, October 19, 2002 17:47 PM
To: Felipe W Damasio
Cc: Paul Hernandez; Linux-net; netdev@oss.sgi.com
Subject: Re: NIC on 2.4.19 SMP


Felipe W Damasio wrote:
> On Fri, 2002-10-18 at 16:57, Paul Hernandez wrote:
> 
>>Hello,
>>
>>It was suggested to me that I forward this issue to you both.
>>
>>OS:                                   2.4.19.SuSE  SMP
>>Motherboard:                    Intel Dual P4 Xeon Server board SE7500CW2
>>(latest bios off Intel site)
>>On-borad LAN controller:  Intel 82557/8/9 [Ether Pro 100] (rev 0d)
>>Addional NIC's tried:        3-COM 3C-905C-TX-M, Netgear FA311
>>
>>dmesg output:
>>
>>e100: eth0: Intel(R) 8255x-based Ethernet Adapter
> 
> 
>>SIOCGMIIPHY on eth0 failed:
>>Operation not supported
>>no MII interfaces found
> 
> 
> 	Try using the eepro100.c driver from the kernel, and not the one from
> Intel (the driver from the kernel supports SIOCGMIIPHY).
> 
> 	Though it does not seem a problem with the driver, you should try using
> the one from the kernel and see if it helps.


I agree that comparison is useful, though it should be pointed out that 
ethtool is preferred for e100...

	Jeff

RE: NIC on 2.4.19 SMP (mii-diag output)

[Paul Hernandez]

Jeff and Felipe,

Here is the mii-diag output. Note that this same machine running SuSE 8.0
(2.4.18.SuSE-SMP) worked correctly with this on-board eepro100 LAN.
Unfortunantely I had to move forward to 2.4.19.SuSE-SMP in order to
correct (and did) a problem with 2.4.18 not recognizing the new ide
controller on this new motherboard and it only ran pio mode .IDE  DMA works
fine
now with 2.4.19.SuSE-SMP but LAN fails (with three different vendor
boards) . The second on-board controller is a Promise FastTrack100 RAID
which I also managed to get working on 2.4.18.SuSE-SMP but now fails as
well on 2.4.19 with a bunch of "lost interrupts" messages when it tries to
access drives on it.

Servers me right for buying such a young motherboard.

Thanks for letting me vent a bit.  ;-)

			Paul

linux19:~ # mii-diag -v eth0
mii-diag.c:v2.02 5/21/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
 Basic mode control register 0x3000: Auto-negotiation enabled.
 Basic mode status register 0x7809 ... 7809.
   Link status: not established.
   This transceiver is capable of  100baseTx-FD 100baseTx 10baseT-FD
10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
   End of basic transceiver information.

 MII PHY #1 transceiver registers:
   3000 7809 02a8 0154 05e1 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0001 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0010 0000 0000 0000.
 Basic mode control register 0x3000: Auto-negotiation enabled.
 Basic mode status register 0x7809 ... 7809.
   Link status: not established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
 Vendor ID is 00:aa:00:--:--:--, model 21 rev. 4.
   No specific information is known about this transceiver type.
 I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD
10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0000:.
   Negotiation did not complete.




-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Saturday, October 19, 2002 5:47 PM
To: Felipe W Damasio
Cc: Paul Hernandez; Linux-net; netdev@oss.sgi.com
Subject: Re: NIC on 2.4.19 SMP


Felipe W Damasio wrote:
> On Fri, 2002-10-18 at 16:57, Paul Hernandez wrote:
>
>>Hello,
>>
>>It was suggested to me that I forward this issue to you both.
>>
>>OS:                                   2.4.19.SuSE  SMP
>>Motherboard:                    Intel Dual P4 Xeon Server board SE7500CW2
>>(latest bios off Intel site)
>>On-borad LAN controller:  Intel 82557/8/9 [Ether Pro 100] (rev 0d)
>>Addional NIC's tried:        3-COM 3C-905C-TX-M, Netgear FA311
>>
>>dmesg output:
>>
>>e100: eth0: Intel(R) 8255x-based Ethernet Adapter
>
>
>>SIOCGMIIPHY on eth0 failed:
>>Operation not supported
>>no MII interfaces found
>
>
> 	Try using the eepro100.c driver from the kernel, and not the one from
> Intel (the driver from the kernel supports SIOCGMIIPHY).
>
> 	Though it does not seem a problem with the driver, you should try using
> the one from the kernel and see if it helps.


I agree that comparison is useful, though it should be pointed out that
ethtool is preferred for e100...

	Jeff

RE: NIC on 2.4.19 SMP (mii-diag output)

[Paul Hernandez]

lsmod shows its using e100. version .13a

eepro100.c is v1.09j-t.

-----Original Message-----
From: Paul Hernandez [mailto:ph@digitalquake.com]
Sent: Monday, October 21, 2002 8:16 AM
To: Jeff Garzik; Felipe W Damasio
Cc: Linux-net; netdev@oss.sgi.com
Subject: RE: NIC on 2.4.19 SMP (mii-diag output)



Jeff and Felipe,

Here is the mii-diag output. Note that this same machine running SuSE 8.0
(2.4.18.SuSE-SMP) worked correctly with this on-board eepro100 LAN.
Unfortunantely I had to move forward to 2.4.19.SuSE-SMP in order to
correct (and did) a problem with 2.4.18 not recognizing the new ide
controller on this new motherboard and it only ran pio mode .IDE  DMA works
fine
now with 2.4.19.SuSE-SMP but LAN fails (with three different vendor
boards) . The second on-board controller is a Promise FastTrack100 RAID
which I also managed to get working on 2.4.18.SuSE-SMP but now fails as
well on 2.4.19 with a bunch of "lost interrupts" messages when it tries to
access drives on it.

Servers me right for buying such a young motherboard.

Thanks for letting me vent a bit.  ;-)

			Paul

linux19:~ # mii-diag -v eth0
mii-diag.c:v2.02 5/21/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
 Basic mode control register 0x3000: Auto-negotiation enabled.
 Basic mode status register 0x7809 ... 7809.
   Link status: not established.
   This transceiver is capable of  100baseTx-FD 100baseTx 10baseT-FD
10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
   End of basic transceiver information.

 MII PHY #1 transceiver registers:
   3000 7809 02a8 0154 05e1 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0001 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0010 0000 0000 0000.
 Basic mode control register 0x3000: Auto-negotiation enabled.
 Basic mode status register 0x7809 ... 7809.
   Link status: not established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
 Vendor ID is 00:aa:00:--:--:--, model 21 rev. 4.
   No specific information is known about this transceiver type.
 I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD
10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0000:.
   Negotiation did not complete.




-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Saturday, October 19, 2002 5:47 PM
To: Felipe W Damasio
Cc: Paul Hernandez; Linux-net; netdev@oss.sgi.com
Subject: Re: NIC on 2.4.19 SMP


Felipe W Damasio wrote:
> On Fri, 2002-10-18 at 16:57, Paul Hernandez wrote:
>
>>Hello,
>>
>>It was suggested to me that I forward this issue to you both.
>>
>>OS:                                   2.4.19.SuSE  SMP
>>Motherboard:                    Intel Dual P4 Xeon Server board SE7500CW2
>>(latest bios off Intel site)
>>On-borad LAN controller:  Intel 82557/8/9 [Ether Pro 100] (rev 0d)
>>Addional NIC's tried:        3-COM 3C-905C-TX-M, Netgear FA311
>>
>>dmesg output:
>>
>>e100: eth0: Intel(R) 8255x-based Ethernet Adapter
>
>
>>SIOCGMIIPHY on eth0 failed:
>>Operation not supported
>>no MII interfaces found
>
>
> 	Try using the eepro100.c driver from the kernel, and not the one from
> Intel (the driver from the kernel supports SIOCGMIIPHY).
>
> 	Though it does not seem a problem with the driver, you should try using
> the one from the kernel and see if it helps.


I agree that comparison is useful, though it should be pointed out that
ethtool is preferred for e100...

	Jeff

RE: NIC on 2.4.19 SMP (mii-diag output)

[Felipe W Damasio]

On Mon, 2002-10-21 at 15:16, Paul Hernandez wrote:
>  I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD
> 10baseT
>    Advertising no additional info pages.
>    IEEE 802.3 CSMA/CD protocol.
>  Link partner capability is 0000:.
>    Negotiation did not complete.

	The link partner is not advertising it's capabilities.

	Can you reproduce this bug with 2.4.19 stock?

Felipe

RE: NIC on 2.4.19 SMP (mii-diag output)

[Donald Becker]

On 22 Oct 2002, Felipe W Damasio wrote:

> On Mon, 2002-10-21 at 15:16, Paul Hernandez wrote:
> >  I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD
> > 10baseT
> >    Advertising no additional info pages.
> >    IEEE 802.3 CSMA/CD protocol.
> >  Link partner capability is 0000:.
> >    Negotiation did not complete.
> 
> 	The link partner is not advertising it's capabilities.

No! There is not link partner.

0000 is the default value for the register when there is no negotiation
going on.
If you have link beat _and_ the register is 0000, then no
autonegotiation took place.
If the link partner advertised "not capable of anything", the register
will report 0001.

-- 
Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993

RE: NIC on 2.4.19 SMP (mii-diag output)

[Paul Hernandez]

All,

Just tried 2.4.20-pre11 and all NIC issues seem to be resolved.
Both eepro100 and e100 drivers work correctly.

			Paul

-----Original Message-----
From: Donald Becker [mailto:becker@scyld.com]
Sent: Tuesday, October 22, 2002 7:21 PM
To: Felipe W Damasio
Cc: Paul Hernandez; Jeff Garzik; Linux-net; netdev@oss.sgi.com
Subject: RE: NIC on 2.4.19 SMP (mii-diag output)


On 22 Oct 2002, Felipe W Damasio wrote:

> On Mon, 2002-10-21 at 15:16, Paul Hernandez wrote:
> >  I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD
> > 10baseT
> >    Advertising no additional info pages.
> >    IEEE 802.3 CSMA/CD protocol.
> >  Link partner capability is 0000:.
> >    Negotiation did not complete.
> 
> 	The link partner is not advertising it's capabilities.

No! There is not link partner.

0000 is the default value for the register when there is no negotiation
going on.
If you have link beat _and_ the register is 0000, then no
autonegotiation took place.
If the link partner advertised "not capable of anything", the register
will report 0001.

-- 
Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993

RE: NIC on 2.4.19 SMP

[Paul Hernandez]

Ok, I'll send the MII-diag output when I get into
work in about an hour.

			Paul

-----Original Message-----
From: Felipe W Damasio [mailto:felipewd@terra.com.br]
Sent: Saturday, October 19, 2002 14:49 PM
To: Paul Hernandez
Cc: Linux-net; netdev@oss.sgi.com
Subject: Re: NIC on 2.4.19 SMP


On Fri, 2002-10-18 at 16:57, Paul Hernandez wrote:
> Hello,
> 
> It was suggested to me that I forward this issue to you both.
> 
> OS:                                   2.4.19.SuSE  SMP
> Motherboard:                    Intel Dual P4 Xeon Server board SE7500CW2
> (latest bios off Intel site)
> On-borad LAN controller:  Intel 82557/8/9 [Ether Pro 100] (rev 0d)
> Addional NIC's tried:        3-COM 3C-905C-TX-M, Netgear FA311
> 
> dmesg output:
> 
> e100: eth0: Intel(R) 8255x-based Ethernet Adapter

> SIOCGMIIPHY on eth0 failed:
> Operation not supported
> no MII interfaces found

	Try using the eepro100.c driver from the kernel, and not the one from
Intel (the driver from the kernel supports SIOCGMIIPHY).

	Though it does not seem a problem with the driver, you should try using
the one from the kernel and see if it helps.

	If it doesn't, reply this mail with the mii-diag output (and driver
version).

Felipe

RE: NIC on 2.4.19 SMP (mii-diag output)

[Feldman, Scott]

Paul wrote: 
> Just tried 2.4.20-pre11 and all NIC issues seem to be 
> resolved. Both eepro100 and e100 drivers work correctly.

Just for kicks, go back to 2.4.19.SuSE-SMP, but this time disable ACPI.
(Set acpi=off in the kernel parameters SuSE's bootloader).  Do the nics
work?

We've seen issues on some of these newer systems with multiple IO-APICS
where the interrupts get masked off when ACPI is enabled. 

-scott