From: Jonathan Nieder <jrnieder@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Richard Kettlewell <rjk@greenend.org.uk>,
Johannes Stezenbach <js@sig21.net>,
linux-wireless@vger.kernel.org, debian-kernel@lists.debian.org,
Ivo Van Doorn <ivdoorn@gmail.com>
Subject: Re: High network latency with ralink usb wireless device
Date: Tue, 24 Apr 2012 00:21:06 -0500 [thread overview]
Message-ID: <20120424052106.GA19023@burratino> (raw)
In-Reply-To: <4D85C506.1060003@greenend.org.uk>
Hi Ben,
About a year ago, Richard Kettlewell wrote[1]:
> On 19/03/2011 22:31, Johannes Stezenbach wrote:
>> I sent a patch to disable power save by default, but then work started
>> to fix it instead, but then stalled. Seems like 2.6.38 shipped with
>> broken power save enabled by default. Plese read the discussion
>> following my RFC patch:
>> http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2011-January/thread.html#3017
>>
>> You can test if power saving causes your issue by disabling
>> it with "iwconfig wlan0 power off".
>
> That does the trick - thanks!
Therefore ever since version 2.6.38-2, Debian kernels have had
powersaving disabled on rt2800usb devices.
I think we should revisit this in light of
v3.0-rc2~7^2~16^2~190 rt2x00: Add autowake support for USB hardware
(2011-04-30)
though I wouldn't be surprised if testing ends up revealing some
followup patches introduced after v3.2 to be needed for it to work
well. What do you think?
Thanks,
Jonathan
[1] http://bugs.debian.org/618930
prev parent reply other threads:[~2012-04-24 5:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D84E433.70001@greenend.org.uk>
[not found] ` <1300555815.26693.83.camel@localhost>
2011-03-19 17:49 ` Bug#618930: High network latency with ralink usb wireless device Richard Kettlewell
2011-03-19 22:31 ` Johannes Stezenbach
2011-03-19 23:32 ` Walter Goldens
2011-03-20 9:12 ` Richard Kettlewell
2012-04-24 5:21 ` Jonathan Nieder [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120424052106.GA19023@burratino \
--to=jrnieder@gmail.com \
--cc=ben@decadent.org.uk \
--cc=debian-kernel@lists.debian.org \
--cc=ivdoorn@gmail.com \
--cc=js@sig21.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rjk@greenend.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).