Bug 65097
| Summary: | orinoco error messages: Tx error, status 1 | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Chris Liebman <liebman> |
| Component: | kernel | Assignee: | Jeff Garzik <jgarzik> |
| Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | michel.salim, peterm, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-06-07 18:40:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Chris Liebman
2002-05-17 14:00:46 UTC
I see this very often when using SMC2602W PCI PLX (orinoco-plx) and SMC2632W (orinoco-cs) cards. Both are based on the prism2 chip, but seems to be completely incompatible with the wvlan driver. What network card were you using when you have those many errors? its an Orinoco gold card (Lucent) I also see the following when the card is inserted: eth1: error -5 reading info frame. Frame dropped. and the following during use: May 20 13:33:56 xyzzy kernel: NETDEV WATCHDOG: eth1: transmit timed out May 20 13:33:56 xyzzy kernel: eth1: Tx timeout! Resetting card. May 20 13:33:56 xyzzy kernel: eth1: Tx error, status 4 (FID=00BE) May 20 13:33:56 xyzzy kernel: eth1: Tx error, status 4 (FID=00E5) May 20 13:33:56 xyzzy kernel: eth1: Tx error, status 4 (FID=00F7) May 20 13:33:56 xyzzy kernel: eth1: Tx error, status 4 (FID=0109) May 20 13:34:45 xyzzy kernel: eth1: Tx error, status 1 (FID=0657) May 20 13:35:36 xyzzy kernel: NETDEV WATCHDOG: eth1: transmit timed out May 20 13:35:36 xyzzy kernel: eth1: Tx timeout! Resetting card. May 20 13:35:36 xyzzy kernel: eth1: Tx error, status 4 (FID=00BE) May 20 13:35:36 xyzzy kernel: eth1: Tx error, status 4 (FID=00E5) May 20 13:35:36 xyzzy kernel: eth1: Tx error, status 4 (FID=00F7) May 20 13:35:36 xyzzy kernel: eth1: Tx error, status 4 (FID=0109) May 20 13:38:28 xyzzy kernel: eth1: Tx error, status 1 (FID=0123) May 20 13:39:10 xyzzy kernel: eth1: Tx error, status 1 (FID=03BC) May 20 13:40:46 xyzzy kernel: eth1: Tx error, status 1 (FID=0161) May 20 14:49:43 xyzzy kernel: eth1: Tx error, status 1 (FID=0208) May 20 14:52:02 xyzzy kernel: eth1: Tx error, status 1 (FID=043F) Upgrading to kernel-2.4.18-5 stopped the errors for me. I am using an Actiontec PCI card, lspci output as follow: 02:06.0 Network controller: Harris Semiconductor Prism 2.5 Wavelan chipset (rev 01) Using orinoco_pci, I get those dreaded Tx messages after a few pings (funnily, the first time around, i.e. network device not enabled during boot, it survived a few minutes) using the SMP kernel. It's stable using the UP kernel though - problems with locking? HTH, Michel Oops. Meant to submit it for RH8 should be fixed in current erratum with majorly updated driver |