From: "John W. Linville" <linville@tuxdriver.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: iwlwifi no authentication with AP - Re: pull request: wireless-next 2014-09-08
Date: Tue, 9 Sep 2014 15:52:32 -0400 [thread overview]
Message-ID: <20140909195232.GO29412@tuxdriver.com> (raw)
In-Reply-To: <540F5927.7000306@hartkopp.net>
On Tue, Sep 09, 2014 at 09:46:47PM +0200, Oliver Hartkopp wrote:
> Hello John, all,
>
> on my i7 Laptop with iwlwifi the latest net-next does not connect to my access point:
>
> [ 10.305284] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
> [ 10.312179] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
> [ 10.524936] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
> [ 10.531762] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
> [ 10.614189] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 17.097238] wlan0: authenticate with 84:c9:b2:d5:87:80
> [ 17.130120] wlan0: send auth to 84:c9:b2:d5:87:80 (try 1/3)
> [ 17.922281] wlan0: send auth to 84:c9:b2:d5:87:80 (try 2/3)
> [ 18.935272] wlan0: send auth to 84:c9:b2:d5:87:80 (try 3/3)
> [ 19.936236] wlan0: authentication with 84:c9:b2:d5:87:80 timed out
> [ 21.962337] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 0
> [ 21.962348] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 3
> [ 21.962413] iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> [ 21.962455] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
> [ 21.962491] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x00000000
> [ 21.962528] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
> [ 21.962564] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x00000000
> [ 21.962600] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
> [ 21.962636] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
> [ 21.962673] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
> [ 21.962709] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x0070402f
> [ 21.962790] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [0,3]
> [ 21.962869] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [0,0]
> [ 21.962949] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [0,0]
> [ 21.963030] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.963109] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 7 ra_tid 0x0000 [48,48]
> [ 21.963189] iwlwifi 0000:02:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.963270] iwlwifi 0000:02:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.963350] iwlwifi 0000:02:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.963428] iwlwifi 0000:02:00.0: Q 8 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.963508] iwlwifi 0000:02:00.0: Q 9 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.963588] iwlwifi 0000:02:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.963669] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.963750] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.963829] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.963909] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.963988] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.964069] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.964149] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.964228] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 21.964308] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
> [ 22.116816] wlan0: authenticate with xx:xx:xx:xx:xx:xx
> [ 22.155887] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
>
> (..)
>
> and again and again ...
>
> Mainly this is the changing stuff in the following dmesg output:
>
> [ 21.962348] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 3
> [ 26.951325] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 6
> [ 34.979316] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 9
> [ 39.964287] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 12
> [ 47.984243] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 15
> [ 55.984240] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 18
> [ 60.981221] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 21
> [ 73.878064] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 24
> [ 86.342476] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 27
> [ 98.770854] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 30
> [ 111.287320] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 33
> [ 121.045034] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 36
>
> 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)
>
> Any idea?
>
> Regards,
> Oliver
Hopefully the Intel guys are listening. As a hunch, what sort of
encryption are you using?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2014-09-09 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 19:16 pull request: wireless-next 2014-09-08 John W. Linville
2014-09-08 23:44 ` David Miller
2014-09-09 19:46 ` iwlwifi no authentication with AP - " Oliver Hartkopp
2014-09-09 19:52 ` John W. Linville [this message]
[not found] ` <20140909195232.GO29412-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2014-09-09 20:15 ` Oliver Hartkopp
2014-09-09 20:02 ` Emmanuel Grumbach
[not found] ` <CANUX_P3n0v1SzfbYuaAsE4TY7Hz_wo2Fb9SmHVNyFOC9hDhwdg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-09 20:23 ` Oliver Hartkopp
2014-09-09 22:07 ` Vadim Kochan
[not found] ` <CAMw6YJLeO1JZeY6hNe-TXOS56b-otk+htt5VPPor+9iYCQz53Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-10 5:01 ` Oliver Hartkopp
2014-09-10 8:24 ` Emmanuel Grumbach
[not found] ` <CANUX_P3kOetqEneHgqoCDN4c85SQYD-G=mQj_o1c_TvKmE5psA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-10 9:16 ` Vadim Kochan
[not found] ` <CAMw6YJKgVVnDrn1X7atemC1r9kwvsr3PQDs4qx5KDeeNy-P3VA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-10 9:23 ` Oliver Hartkopp
2014-09-10 16:31 ` Oliver Hartkopp
2014-09-14 18:08 ` Kalle Valo
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=20140909195232.GO29412@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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).