linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@sig21.net>
To: Richard Kettlewell <rjk@greenend.org.uk>
Cc: linux-wireless@vger.kernel.org, 618930@bugs.debian.org,
	Ivo Van Doorn <ivdoorn@gmail.com>
Subject: Re: Bug#618930: High network latency with ralink usb wireless device
Date: Sat, 19 Mar 2011 23:31:59 +0100	[thread overview]
Message-ID: <20110319223159.GA19576@sig21.net> (raw)
In-Reply-To: <4D84EC90.4090803@greenend.org.uk>

On Sat, Mar 19, 2011 at 05:49:04PM +0000, Richard Kettlewell wrote:
> (see also bugs.debian.org/618930
...
> I have a TP-Link TL-WN321G USB wireless adapter, which is a badged
> Ralink RT2070.  Under Debian's 2.6.32 this worked smoothly with
> rt2870sta.  On upgrading to Debian's 2.6.38, however, only rt2800usb
> was available and with that I found that ping latency is around
> 600ms.
...
>           Power Management:on

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".

Johannes

  reply	other threads:[~2011-03-19 22:32 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 [this message]
2011-03-19 23:32       ` Walter Goldens
2011-03-20  9:12       ` Richard Kettlewell
2012-04-24  5:21         ` Jonathan Nieder

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=20110319223159.GA19576@sig21.net \
    --to=js@sig21.net \
    --cc=618930@bugs.debian.org \
    --cc=ivdoorn@gmail.com \
    --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).