From: Larry Finger <Larry.Finger@lwfinger.net>
To: Julian Wollrath <jwollrath@web.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: WARNING: at net/wireless/mlme.c:517
Date: Wed, 02 Jan 2013 11:00:52 -0600 [thread overview]
Message-ID: <50E467C4.6030602@lwfinger.net> (raw)
In-Reply-To: <20130102120002.691dbbb4@ilfaris>
On 01/02/2013 05:00 AM, Julian Wollrath wrote:
> Below is the output of a short time with debug=4 from a period where
> the interface did not manage to connect properly to the AP. Since I have
> no LED which indicates anything the lines that state
> "rtl8192ce:rtl92ce_led_control() [...]" do not seem necessary but I
> suspect there is no way to detect if there really is a state LED or is
> it?
Thanks for the debug output. There is no way for the driver to detect if there
is an actual LED attached to that pin of the mini-PCIe connector, thus we
program it as if one were available.
>
> The other thing, which catched my eye, were the following repeated messages:
> rtl8192ce:rtl92ce_set_hw_reg():<0-0> HW_VAR_SLOT_TIME 14
> rtl8192c_common:rtl92c_phy_sw_chnl():<0-0> sw_chnl_inprogress false schdule workitem
That sequence is due to scanning and is completely normal.
I have not looked at detail at the debug listing, but I do have additional
questions. None of your Emails on this subject mention anything about the AP.
What make/model is it? What firmware is it running? Is it 802.11g or 802.11n?
What are the details of the encryption? The device authenticates but is never
able to associate after that.
Thanks,
Larry
next prev parent reply other threads:[~2013-01-02 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 14:45 WARNING: at net/wireless/mlme.c:517 Julian Wollrath
2013-01-01 18:06 ` Larry Finger
2013-01-01 22:15 ` Julian Wollrath
2013-01-01 22:28 ` Larry Finger
2013-01-02 11:00 ` Julian Wollrath
2013-01-02 17:00 ` Larry Finger [this message]
2013-01-03 9:31 ` Julian Wollrath
2013-01-07 15:06 ` Julian Wollrath
2013-01-04 13:30 ` Johannes Berg
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=50E467C4.6030602@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=jwollrath@web.de \
--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).