Bug 9301 - sky2 driver after resume transmits data very slowly
Summary: sky2 driver after resume transmits data very slowly
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Jeff Garzik
URL:
Keywords:
Depends on:
Blocks: 7216
  Show dependency tree
 
Reported: 2007-11-03 16:29 UTC by Andrew Zabolotny
Modified: 2007-11-05 11:06 UTC (History)
3 users (show)

See Also:
Kernel Version: kernel-2.6.22.9-91.fc7
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Andrew Zabolotny 2007-11-03 16:29:05 UTC
Most recent kernel where this bug did not occur: always happened from time to time, but with latest kernels (2.6.21 and 22) it got worse (100% after resume)
Distribution: Fedora 7 x86_64 with latest updates
Hardware Environment: Gigabyte P965 DS3, Core Duo 2 CPU, 03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 22)
Problem Description:
After booting the system I can transmit files to any computer on my LAN via FTP with a maximal possible speed on my 100Mbit LAN (about 12Mb/s). However, if I put the computer into the sleep mode (echo mem >/sys/power/state), after turning the computer back on again the upload speed drops to about 100 kilobytes per second.

Steps to reproduce:
1. Make sure you can upload a file to some LAN FTP server with high speed.
2. Switch the computer into sleep mode with echo mem > /sys/power/state or equivalent (usually I do this via Gnome's System menu).
3. After the computer turns off, turn it back on.
4. Try to upload something to same LAN FTP server. I usually get speeds around 100k/s.
Comment 1 Andrew Zabolotny 2007-11-03 16:30:20 UTC
Forgot to add: there is a workaround, if you do:

service network stop; rmmod sky2; service network start

the network is back at full speed.
Comment 2 Rafael J. Wysocki 2007-11-04 04:42:54 UTC
Can you test the 2.6.23 kernel, please?
Comment 3 Andrew Zabolotny 2007-11-05 11:06:48 UTC
Indeed, 2.6.23 fixed it. I should think of this before reporting it. Thank you, I'll close the report.

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