All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bikram Assal" <bikram.assal@wku.edu>
To: linux-kernel@vger.kernel.org
Subject: eepro100 NIC driver. any bug ?
Date: Mon, 14 Jun 2004 16:31:09 -0500	[thread overview]
Message-ID: <web-68980662@mailadmin.wku.edu> (raw)

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/

             reply	other threads:[~2004-06-14 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14 21:31 Bikram Assal [this message]
2004-06-15  6:45 ` eepro100 NIC driver. any bug ? Meelis Roos
2004-06-21 17:59   ` Skylar Thompson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=web-68980662@mailadmin.wku.edu \
    --to=bikram.assal@wku.edu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.