From: Nathan Schulte <nmschulte@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: users@rt2x00.serialmonkey.com,
Gertjan van Wingerde <gwingerde@gmail.com>,
598144@bugs.debian.org
Subject: Re: rt2500pci: very low transfers and link quality
Date: Wed, 08 Aug 2012 01:49:47 -0500 [thread overview]
Message-ID: <50220C0B.9080009@gmail.com> (raw)
In-Reply-To: <20120806215236.GA268@mannheim-rule.local>
Hi folks.
I've been requested to report a bug that I've discovered regarding
troubles with the rt2500pci kernel module. As the subject suggests,
with my card I'm receiving very poor transfer rate and link quality.
The Debian bug report for this issue can be found here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598144
Initially, I noticed the following line repeated in the logs:
> phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
which led me to the (closed) Ubuntu bug report:
https://bugs.launchpad.net/bugs/456977
The initial error message appears to be a red herring of sorts, as it
can be quieted by turning off power control for the interface:
# iwconfig wlan0 power off
Even with the message silenced, I am still receiving poor link
throughput and quality. The initial bug reporter noticed the issues
with kernel 2.6.32, and I've experienced it with 2.6.32 and 3.2.21 (as
packaged by Debian). I tried with 3.5 from Debian experimental, but I
receive a kernel panic (after which the kernel becomes unresponsive)
whenever I bring up the interface. This is all noted in the bug report
log where copies of the kernel logs can be found.
The request for upstream notification can be seen below. Please let me
know how I can help!
--
Jonathan Nieder wrote:
> Afterwards, please report this upstream (regardless of
> the result) to linux-wireless@vger.kernel.org, cc-ing
> users@rt2x00.serialmonkey.com, Gertjan van Wingerde
> <gwingerde@gmail.com>, and either me or this bug log so we can track
> it.
>
> Then hopefully someone upstream can provide commands or a patch to try
> to track down the cause and work toward a fix.
Thanks!
--
Nate
parent reply other threads:[~2012-08-08 6:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20120806215236.GA268@mannheim-rule.local>]
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=50220C0B.9080009@gmail.com \
--to=nmschulte@gmail.com \
--cc=598144@bugs.debian.org \
--cc=gwingerde@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.com \
/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).