linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: Florian Klink <flokli@flokli.de>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: commit 062bee448bd539580ef9f64efe50fdfe04eeb103 broke my iwlagn 5100
Date: Wed, 14 Jul 2010 19:36:45 +0200	[thread overview]
Message-ID: <1279129005.3723.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1279128461.19725.34.camel@wwguy-ubuntu>

On Wed, 2010-07-14 at 10:27 -0700, Guy, Wey-Yi wrote:
> Johannes,
> 
> On Wed, 2010-07-14 at 09:36 -0700, Florian Klink wrote:
> > Hi,
> > 
> > I did a dmesg with 2.6.35-rc5 and debug=0x43fff.
> > You can get it here: http://pastebin.com/Q6eCdPZR
> 
> > 
> > 
> based on the log sent by Florian, I did not see bss_info_change with
> current BSSID from mac80211. any thought?
> 
> I am expected to see something like this,
> 
> [165796.572969] ieee80211 phy3: U iwl_bss_info_changed changes =
> 0xFD                                                                    
> [165796.572972] ieee80211 phy3: U iwl_bss_info_changed BSSID
> 00:25:9c:d0:9f:e1                                                           
> [165796.572976] ieee80211 phy3: U iwl_bss_info_changed ERP_PREAMBLE 1 

That'd only happen _after_ association, not before, and assoc fails
here.

johannes


  reply	other threads:[~2010-07-14 17:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14  9:33 commit 062bee448bd539580ef9f64efe50fdfe04eeb103 broke my iwlagn 5100 Florian Klink
2010-07-14 10:00 ` Johannes Berg
2010-07-14 10:06   ` Florian Klink
2010-07-14 15:28     ` Guy, Wey-Yi
2010-07-14 16:36       ` Florian Klink
2010-07-14 17:27         ` Guy, Wey-Yi
2010-07-14 17:36           ` Johannes Berg [this message]
2010-07-14 17:44             ` Guy, Wey-Yi
  -- strict thread matches above, loose matches on Subject: below --
2010-07-16 23:22 Florian Klink
2010-07-16 23:49 ` Guy, Wey-Yi
2010-07-16 23:48   ` Florian Klink

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=1279129005.3723.8.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=flokli@flokli.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wey-yi.w.guy@intel.com \
    /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).