b44 driver constantly disconnects with heavy use
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: linux-image-
The b44 ethernet driver that comes with the new 2.6.27-7-generic kernel (Ubuntu Intrepid) constantly disconnects the link when using it heavily (during rsync backups). The link resumes, but the hickup is very noticeable.
For normal use of the ethernet, there is no problem. Only with rsync, when it's transfering 7-8 mbps under a 100Mbps network. With Hardy this has never happened on the same machine, same network cable.
dmesg shows:
[...]
[10095.996874] b44: eth0: powering down PHY
[10096.804102] b44: eth0: Link is down.
[10098.804193] b44: eth0: Link is up at 100 Mbps, full duplex.
[10098.804207] b44: eth0: Flow control is off for TX and off for RX.
[10104.843424] b44: eth0: powering down PHY
[10105.804104] b44: eth0: Link is down.
[10107.804191] b44: eth0: Link is up at 100 Mbps, full duplex.
[10107.804206] b44: eth0: Flow control is off for TX and off for RX.
[10112.956742] b44: eth0: powering down PHY
[10113.804113] b44: eth0: Link is down.
[10115.804186] b44: eth0: Link is up at 100 Mbps, full duplex.
[10115.804201] b44: eth0: Flow control is off for TX and off for RX.
[10119.556411] b44: eth0: powering down PHY
[10119.804103] b44: eth0: Link is down.
[10122.804186] b44: eth0: Link is up at 100 Mbps, full duplex.
[10122.804199] b44: eth0: Flow control is off for TX and off for RX.
| Chris Coulson (chrisccoulson) wrote | #1 |
| Changed in linux: | |
| status: | New → Invalid |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 279102, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.