Bug 249110 - prism54pci: "phy0: tx overflow." when network traffic is heavy
Summary: prism54pci: "phy0: tx overflow." when network traffic is heavy
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 7
Hardware: All Linux
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-20 22:32 UTC by Mike Bonnet
Modified: 2008-01-09 17:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-09 17:05:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Mike Bonnet 2007-07-20 22:32:14 UTC
Description of problem:
When transferring a lot of data over a prism54pci interface (Netgear WG511 v1
(softmac)), the interface will eventually (sometimes minutes, sometimes hours)
stop transferring any data, and a "kernel: phy0: tx overflow." message will
appear in /var/log/messages.  The interface will be unusable until the card is
ejected and reinserted into the pccard slot, causing it to get reinitialized.

Version-Release number of selected component (if applicable):
prism54pci firmware version

How reproducible:

Steps to Reproduce:
1. use a prism54pci interface
2. transfer a lot of data over it
Actual results:
"phy0: tx overflow." message appears, interface no longer transfers data

Expected results:
no "tx overflow" message, interface continues to work

Additional info:

Comment 1 Christopher Brown 2007-09-20 10:48:54 UTC

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.


I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.


Comment 2 Christopher Brown 2008-01-09 17:05:25 UTC
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.

Note You need to log in before you can comment on or make changes to this bug.