linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Blue Glacier <blueglacier414@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: "No association and the time event is over already..."
Date: Sat, 20 Jun 2015 20:33:45 +0200	[thread overview]
Message-ID: <5585B209.3040406@gmail.com> (raw)

Hello,

my Intel Wireless 7265 chip suddenly stopped working. The Network 
Manager shows that I am connected, but I cannot even ping to my home 
router. I didn't change anything on my system.

The output of dmesg looks interesting:

[  507.737606] wlan0: Connection to AP c0:25:06:ce:d2:e9 lost
[  507.806070] cfg80211: Calling CRDA for country: DE
[  508.379770] cfg80211: Calling CRDA for country: DE
[  511.332818] wlan0: authenticate with c0:25:06:ce:d2:e9
[  511.338625] wlan0: send auth to c0:25:06:ce:d2:e9 (try 1/3)
[  511.341600] wlan0: authenticated
[  511.343813] wlan0: associate with c0:25:06:ce:d2:e9 (try 1/3)
[  511.350128] wlan0: RX AssocResp from c0:25:06:ce:d2:e9 (capab=0x431 
status=0 aid=8)
[  511.353700] wlan0: associated
[  511.645582] iwlwifi 0000:03:00.0: No association and the time event 
is over already...
[  511.645642] wlan0: Connection to AP c0:25:06:ce:d2:e9 lost
[  511.688174] cfg80211: Calling CRDA to update world regulatory domain

(repeated numerous times)

I am using Debian 8 Jessie (stable) together with the firmware from your 
server (iwlwifi-7265-9.ucode). The Kernel Version is 3.16.0-4-amd64.

Any idea how to fix this?

Jens
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in

             reply	other threads:[~2015-06-20 18:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-20 18:33 Blue Glacier [this message]
2015-06-20 20:01 ` "No association and the time event is over already..." Emmanuel Grumbach
2015-06-20 22:27   ` Blue Glacier
2015-06-21  6:22     ` Emmanuel Grumbach

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=5585B209.3040406@gmail.com \
    --to=blueglacier414@gmail.com \
    --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).