linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Borislav Petkov <bp@alien8.de>
Cc: 李朝明 <chaoming_li@realsil.com.cn>,
	linux-wireless@vger.kernel.org,
	'LKML' <linux-kernel@vger.kernel.org>
Subject: Re: 答复: 答复: 答复: 3.1-rc6+ rtl8192se issue
Date: Fri, 23 Sep 2011 08:50:41 -0500	[thread overview]
Message-ID: <4E7C8EB1.5050007@lwfinger.net> (raw)
In-Reply-To: <20110923103339.GA26078@gere.osrc.amd.com>

On 09/23/2011 05:33 AM, Borislav Petkov wrote:
> On Fri, Sep 23, 2011 at 06:21:07PM +0800, 李朝明 wrote:
>> Please set ips =0 and try again..
>
> What does that mean?
>
> I can trigger the grinding-to-a-halt reliably with "ips=0" - it only
> takes a couple of hours of network traffic. Also, I don't want to try
> the driver you sent me because the version in the kernel needs fixing
> not some out-of-tree codebase.

Does the likelihood of the failure change when "ips=0" is used?

The Realtek group made several changes in the driver that Chaoming sent you that 
have not yet been incorporated in the kernel version. If you test that driver, 
we might learn if any of them are important to your problem. As neither of us 
can duplicate your results, it is not possible for us to do those tests.

I agree that we want to fix the kernel version. It is unfortunate that Realtek 
does not generate their improvements as patches to that kernel version, and 
publish them that way, but that is a fact of life. When they produce a new 
version, I have to look at the diff file between it and the previous version and 
test those differences with my devices. Thus far, there have been no changes 
that have any effect on my system, but who knows on yours. Please run the test 
as Chaoming asked you to do.

Thanks,

Larry

  reply	other threads:[~2011-09-23 13:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15 12:44 3.1-rc6+ rtl8192se issue Borislav Petkov
2011-09-15 15:23 ` Larry Finger
2011-09-15 18:41   ` Borislav Petkov
2011-09-16 18:03   ` Borislav Petkov
     [not found]     ` <CD4D8CF16C39438E82FE8241C9AF80F4@realsil.com.cn>
2011-09-19  9:54       ` 答复: " Borislav Petkov
2011-09-19 17:13       ` Borislav Petkov
2011-09-21 18:58       ` Borislav Petkov
     [not found]         ` <791179BCE62F4954AB936E6CAC9CA977@realsil.com.cn>
     [not found]           ` <4E7AAB8B.40900@lwfinger.net>
2011-09-22  7:51             ` 答复: " Borislav Petkov
     [not found]               ` <6452E68488784D0EA32E4BDF1B941EFB@realsil.com.cn>
2011-09-23 10:33                 ` 答复: " Borislav Petkov
2011-09-23 13:50                   ` Larry Finger [this message]
2011-09-23 16:34                   ` Larry Finger
2011-09-28 13:18                     ` Borislav Petkov
2011-09-29  1:57                       ` Larry Finger
2011-10-05 15:15                         ` Borislav Petkov
2011-10-06  2:37                           ` Larry Finger
2011-11-15 13:59                             ` Borislav Petkov

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=4E7C8EB1.5050007@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bp@alien8.de \
    --cc=chaoming_li@realsil.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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).