FS#26108 - Hibernate reduces network bandwidth

Attached to Project: Arch Linux
Opened by Amitav (amitavmohanty01) - Saturday, 24 September 2011, 07:31 GMT
Last edited by Allan McRae (Allan) - Sunday, 03 June 2012, 08:42 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
I am using gridftp to transfer files from one system to another. I have a Gentoo system connected to a Belkin router through ethernet and a laptop having Arch linux connected to the router using wireless (WPA network). I am connected to the internet through the router-cum-modem. After a fresh restart of the laptop, when I try transfers from the Gentoo system, I get transfer rates of around 3.7MB/sec. However, if I hibernate, wake up and try transfers from the same Gentoo system, I get transfer rates of around 1.1MB/sec. Packet loss stays at constant 19% in both cases.

Additional info:
* package version(s): Globus Toolkit 5.0.4
linux 3.0.4-1
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 03 June 2012, 08:42 GMT
Reason for closing:  Works for me
Additional comments about closing:  Reopen if more information
Comment by Amitav (amitavmohanty01) - Monday, 26 September 2011, 22:03 GMT
On Hacker News it was suggested that it is possible that Linux does not reinitialize the wireless chipset in the right way, leading to a performance loss after hibernation.
http://news.ycombinator.com/item?id=3034433
Comment by Jelle van der Waa (jelly) - Thursday, 29 September 2011, 16:52 GMT
This is probably an upstream problem, aka in the drivers report it there.
Comment by Amitav (amitavmohanty01) - Thursday, 29 September 2011, 19:15 GMT
Yes probably this is an upstream bug. However I was wondering if we could narrow it down: whether it is a kernel issue or an issue with broadcom drivers or power management. While talking about it on IRC channels there have been suggestions that this might be caused by inappropriate power management. So, if the bug is narrowed down I can know 'upstream' points to which package.
Comment by Allan McRae (Allan) - Saturday, 02 June 2012, 13:01 GMT
Status?
Comment by Amitav (amitavmohanty01) - Sunday, 03 June 2012, 06:35 GMT
I have not tested it recently so I can't comment on the status. You may close it for now. In case someone else finds it happening, (s)he will reopen it.

Loading...