linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Romosan <romosan@sycorax.lbl.gov>
To: linux-wireless@vger.kernel.org
Subject: iwlwifi unable to reconnect after suspend since v3.9-rc1
Date: Tue, 26 Mar 2013 13:52:39 -0700	[thread overview]
Message-ID: <87li993mug.fsf@sycorax.lbl.gov> (raw)

since v3.9-rc1 i have been unable to reconnect to my access point. the
access point is a netgear n600 and the my card is a Centrino Advanced-N
6205 [Taylor Peak] (rev 34). the last kernel that worked was 3.8. when i
boot up the laptop the connection is established but if i bring down the
network with ifdown then i cannot reconnect. this is what i see in the
logs:

 iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
 iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
 wlan0: authenticate with xx:xx:xx:xx:xx:xx
 wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
 wlan0: send auth to xx:xx:xx:xx:xx:xx (try 2/3)
 wlan0: send auth to xx:xx:xx:xx:xx:xx (try 3/3)
 wlan0: authentication with xx:xx:xx:xx:xx:xx timed out

today i discovered that this happens only if i connect to the 5GHz.
connecting to 2.4GHz works on resume. i tried to do a 'git bisect start
-- drivers/net/wireless' and i ended up with

Bisecting: 0 revisions left to test after this (roughly 0 steps)
[e1a0c6b3a4b27ed5f21291d0bbee2167ec201ef5] mac80211: stop toggling IEEE80211_HT_CAP_SUP_WIDTH_20_40

but i haven't been able to revert it cleanly so i don't know if that's
the problem or not?

any ideas? thanks.

--alex--

-- 
| I believe the moment is at hand when, by a paranoiac and active |
|  advance of the mind, it will be possible (simultaneously with  |
|  automatism and other passive states) to systematize confusion  |
|  and thus to help to discredit completely the world of reality. |

             reply	other threads:[~2013-03-26 20:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 20:52 Alex Romosan [this message]
2013-03-27 13:14 ` iwlwifi unable to reconnect after suspend since v3.9-rc1 Johannes Berg
2013-03-27 17:35   ` Alex Romosan
2013-03-27 17:41     ` Johannes Berg
2013-03-27 18:02       ` Alex Romosan
2013-03-27 19:02         ` Johannes Berg
2013-03-27 19:08           ` Alex Romosan
2013-03-27 19:11             ` Johannes Berg
2013-03-27 19:14             ` Johannes Berg
2013-03-27 19:33               ` Alex Romosan
2013-03-27 19:44                 ` Johannes Berg
2013-03-27 20:03                   ` Alex Romosan
2013-03-27 20:13                     ` Johannes Berg
2013-03-27 20:29                       ` Alex Romosan
2013-03-27 17:42 ` Johannes Berg
2013-03-27 17:48   ` Alex Romosan
2013-03-27 17:54     ` Johannes Berg
2013-03-27 18:58       ` Alex Romosan

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=87li993mug.fsf@sycorax.lbl.gov \
    --to=romosan@sycorax.lbl.gov \
    --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).