From: Hin-Tak Leung <htl10@users.sourceforge.net>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
herton@mandriva.com.br,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: rtl8187b throughput-related regression in 2.6.35.x fixed in 2.6.37.x
Date: Sun, 27 Mar 2011 05:01:23 +0100 [thread overview]
Message-ID: <4D8EB693.5010704@users.sourceforge.net> (raw)
In-Reply-To: <20110318085401.GB2162@redhat.com>
Stanislaw Gruszka wrote:
> On Fri, Mar 18, 2011 at 05:18:25AM +0000, Hin-Tak Leung wrote:
>> Hi Larry/Herton/John,
>>
>> There appears to be some kind of throughput related regression in 2.6.35.x (11-85-ish fedora, current long-term maintainance kernel) which is fixed by putting compat-wireless 2.6.37.x (4) on. I just thought I should mention this, in case somebody files a bug about rtl8187(b) being too slow, that putting compat-wireless on might help.
>>
>> My AP machine was out for almost a year so I have not been using my rtl8187b for a while. When I finally got that fixed, after a while I noticed the throughput between the two machines was low (60KB/s, or 0.5Mb/s, although iwconfig says rate=11Mb/s, etc). Putting compat-wireless on gets me back the throughput I expect from a year ago (400KB/s+ onwards, or a few Mb/s at least). So 2.6.31.x a year ago was okay, 2.6.37.x is okay, but there appear to be something not quite right with 2.6.35.x in the middle. There are too many changes, and it is probably not important since current-ish kernel head is okay.
>
> Would be nice to have this fixed in stable.
>
> We have already one AP mode bug opened:
> http://bugzilla.redhat.com/show_bug.cgi?id=671514
>
> It was recognized that this patch is needed in .35.11 (.35.9 is ok):
> http://git.kernel.org/linus/09a02fdb919876c01e8f05960750a418b3f7fa48
>
> Not sure if this is the same issue, but perhaps you could try above
> patch. If it does not help, could you check if problem is
> 2.6.35.x -> 2.6.35.11 regression?
>
> Stanislaw
>
Just checked again, downloading and using a bunch of compat tar balls. It
appeared that the throughput problem I reported above was fixed between 2.6.37.4
and 2.6.38-rc7. In any case, it does not appear to be the ones you mentioned.
I might spend a bit more time eventually to see what fixes it. The one thing
interesting
about those two versions were Herton's house-keeping
rtl8187: restore anaparam registers after reset with 8187B
rtl8187: fix wrong register initialization in 8187B
and Thadeu Lima de Souza Cascardo
rtl8187b: do not do per packet TX AGC
And the Signal level did seem to change from about -40 dBm to -30
But these are a bit curious how I did get good throughput with 2.6.31.x-ish .
Hin-Tak
next prev parent reply other threads:[~2011-03-27 4:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 5:18 rtl8187b throughput-related regression in 2.6.35.x fixed in 2.6.37.x Hin-Tak Leung
2011-03-18 8:54 ` Stanislaw Gruszka
2011-03-27 4:01 ` Hin-Tak Leung [this message]
2011-04-07 22:04 ` Hin-Tak Leung
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=4D8EB693.5010704@users.sourceforge.net \
--to=htl10@users.sourceforge.net \
--cc=Larry.Finger@lwfinger.net \
--cc=herton@mandriva.com.br \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.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).