Return-path: Received: from mga11.intel.com ([192.55.52.93]:16832 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759483Ab0GPXrk (ORCPT ); Fri, 16 Jul 2010 19:47:40 -0400 Subject: Re: commit 062bee448bd539580ef9f64efe50fdfe04eeb103 broke my iwlagn 5100 From: "Guy, Wey-Yi" To: Florian Klink Cc: Johannes Berg , "linux-wireless@vger.kernel.org" In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Fri, 16 Jul 2010 16:49:10 -0700 Message-ID: <1279324150.8881.12.camel@wwguy-huron> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Florian, On Fri, 2010-07-16 at 16:22 -0700, Florian Klink wrote: > On Wed, 14 Jul 2010 10:44:21 -0700, "Guy, Wey-Yi" > wrote: > > Hi Florian, > > > > On Wed, 2010-07-14 at 10:36 -0700, Johannes Berg wrote: > >> 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. > >> > > Could you try different channel instead of channel 12 to see if the > > problem still there? > > > > Thanks > > Wey > >> > > > Hi, > > very strange, now I can't reproduce the problem anymore, association > works with channel 12 and other ones, too! > I have no idea why it's now working... > > Could this commit affect any link tolerance/timeouts, because I was > able to bisect the problem? > Not sure what happen, but please do let us know if you see the problem pop up again. I do not think this patch should affect the link tolerance. Thanks Wey >