linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Vincent Brillault <gentoo@lerya.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Warnings with ASUS PCE-N15 (RTL8188CE)
Date: Mon, 25 Mar 2013 14:11:27 -0500	[thread overview]
Message-ID: <5150A15F.20600@lwfinger.net> (raw)
In-Reply-To: <20130325182910.GA10274@Fea.lerya.net>

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]

On 03/25/2013 01:29 PM, Vincent Brillault wrote:
> Hi Larry and everyone else on the list,
>
> I've seen your 25 patches and applied them in hope my problems were
> resolved. They are not :'(
>
> I've tried to look further, I think that the root of this problem is in
> core.c, in the rtl_op_bss_info_changed function. This function make a
> call to get_sta on the new bssid. The problem is that at this point, the
> sta is still not inserted, thus cannot be accessed by this method. As
> far as I understand the code, this specific rtl_op_bss_info_changed is
> responsible for setting rtlmac->mode, which explains why this mode is
> never set on my system.

I think the difference in our two systems is in the use of NetworkManager and 
the associated applet. With it, rtl_op_bss_info_changed() does not seem to be 
called before sta is ready.

Attached is a patch that will force mac->mode when sta has not been established. 
Perhaps that will be enough.

It not, I will need to set up your distro and run the wireless exactly the way 
you do to duplicate your results. Please provide the distro name and version, 
the architecture, the sequence of commands, and the contents of any special 
scripts you run.

Larry



[-- Attachment #2: rtlwifi_fix_core --]
[-- Type: text/plain, Size: 477 bytes --]

Index: wireless-testing-save/drivers/net/wireless/rtlwifi/core.c
===================================================================
--- wireless-testing-save.orig/drivers/net/wireless/rtlwifi/core.c
+++ wireless-testing-save/drivers/net/wireless/rtlwifi/core.c
@@ -832,6 +832,7 @@ static void rtl_op_bss_info_changed(stru
 		rcu_read_lock();
 		sta = get_sta(hw, vif, bss_conf->bssid);
 		if (!sta) {
+			mac->mode = WIRELESS_MODE_G;
 			rcu_read_unlock();
 			goto out;
 		}

  reply	other threads:[~2013-03-25 19:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 19:29 Warnings with ASUS PCE-N15 (RTL8188CE) Vincent Brillault
2013-03-08 21:58 ` Vincent Brillault
2013-03-09  1:53   ` Larry Finger
2013-03-09 11:32     ` Vincent Brillault
2013-03-09 18:24       ` Larry Finger
2013-03-11 18:38         ` Vincent Brillault
2013-03-13  8:00           ` Vincent Brillault
2013-03-17 14:12             ` Vincent Brillault
2013-03-25 18:29               ` Vincent Brillault
2013-03-25 19:11                 ` Larry Finger [this message]
2013-03-25 19:51                   ` Vincent Brillault
2013-03-25 20:05                     ` Larry Finger
2013-04-09  9:47                       ` Vincent Brillault
2013-04-09 15:32                         ` Larry Finger
2013-04-09 16:04                           ` Vincent Brillault
2013-04-09 18:03                             ` Larry Finger

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=5150A15F.20600@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=gentoo@lerya.net \
    --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).