eepro100 NIC driver. any bug ?

eepro100 NIC driver. any bug ?

[Bikram Assal]

Hi,

Would you suggest ee100 over eepro100 driver for an INTEL NIC ?

Currently, we are using eepro100 driver on one of our servers that have INTEL NICs installed.

I have come across a situation three times when I had to reboot the server because it hanged and wouldn't respond and next time when I rebooted the server, I did not find any messages in the /var/log/messages file.

On one of these occasions, I could see errors saying, 


kernel: NETDEV WATCHDOG: eth1: transmit timed out
Jun 2 12:56:24 kernel: eth1: Transmit timed out: status f048 0c00 at 1703794288/1703794348 command 200ca000.
Jun 2 12:57:06 kernel: NETDEV WATCHDOG: eth1: transmit timed out
Jun 2 12:57:06 kernel: eth1: Transmit timed out: status f088 0c00 at 1703794348/1703794410 command 0001a000.
Jun 2 12:57:58 kernel: NETDEV WATCHDOG: eth1: transmit timed out
Jun 2 12:57:58 kernel: eth1: Transmit timed out: status f088 0c00 at 1703794410/1703794471 command 0001a000.


I have read documentation on the net mentioning that eepro100 is a deprecated driver and isntead ee100 should be used.

I dont know if I should relate the other hangs on our server with the one when we had these "transmit timed out" errors  show up in the /var/log/messages file.

Please suggest me on this.

Thanks for your help.

- Bikram 
OCA ( Oracle Certified Associate )
Database Specialist, WKU
http://www.wku.edu/~bikram.assal/

Re: eepro100 NIC driver. any bug ?

[Meelis Roos]

BA> Would you suggest ee100 over eepro100 driver for an INTEL NIC ?
BA> 
BA> kernel: NETDEV WATCHDOG: eth1: transmit timed out
BA> Jun 2 12:56:24 kernel: eth1: Transmit timed out: status f048 0c00 at 1703794288/1703794348 command 200ca000.

A co-worker had a very similar problem with eepro100 when I switched his
computer from 100 Mbps fullduplex switch to 10Mbps halfduplex hub. The
problems went away with e100 driver. It was with a revent kernel about a
month ago but I don't remeber whether it was a recent 2.4 or a recent
2.6 kernel. The NIC in question is the onboard NIC of Intel D815EEA2
mainboard.

-- 
Meelis Roos

Re: eepro100 NIC driver. any bug ?

[Skylar Thompson]

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

On Tue, Jun 15, 2004 at 09:45:22AM +0300, Meelis Roos wrote:
> BA> Would you suggest ee100 over eepro100 driver for an INTEL NIC ?
> BA> 
> BA> kernel: NETDEV WATCHDOG: eth1: transmit timed out
> BA> Jun 2 12:56:24 kernel: eth1: Transmit timed out: status f048 0c00 at 1703794288/1703794348 command 200ca000.
> 
> A co-worker had a very similar problem with eepro100 when I switched his
> computer from 100 Mbps fullduplex switch to 10Mbps halfduplex hub. The
> problems went away with e100 driver. It was with a revent kernel about a
> month ago but I don't remeber whether it was a recent 2.4 or a recent
> 2.6 kernel. The NIC in question is the onboard NIC of Intel D815EEA2
> mainboard.

I've also had trouble with the eepro100 driver. I help maintain a 16-node
HPC cluster of VA Linux 2200 2x2 with on-board Intel EtherExpress Pro 100
NICs. During times of high network traffic, the eepro100 driver would just
cause the card to lose its carrier. Switching to the e100 driver solved
this problem.

-- 
-- Skylar Thompson (skylar@cs.earlham.edu)
-- http://www.cs.earlham.edu/~skylar/

[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]