Return-path: Received: from he.sipsolutions.net ([78.46.109.217]:54886 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752722Ab2C1S77 (ORCPT ); Wed, 28 Mar 2012 14:59:59 -0400 Message-ID: <1332961193.3479.40.camel@jlt3.sipsolutions.net> (sfid-20120328_210003_042979_B20854B8) Subject: Re: bss_info_change_notify warning (hacked 3.3.0-rc5+) From: Johannes Berg To: Ben Greear Cc: Bryan Phillippe , linux-wireless Date: Wed, 28 Mar 2012 20:59:53 +0200 In-Reply-To: <4F735EF5.3010708@candelatech.com> References: <4F57B7E6.1050103@candelatech.com> <4F735EF5.3010708@candelatech.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, 2012-03-28 at 11:56 -0700, Ben Greear wrote: > On 03/07/2012 11:45 AM, Bryan Phillippe wrote: > > > > Yes, it's a known problem. It's very reproducible for me on a non-hacked 3.3-rc1 as well: changing from AP to client mode, or setting up multiple APs, or changing from 2.4Ghz to 5Ghz all seem to trigger this warning with various stack traces. > > I'm still seeing this and related warnings on 3.3.0. At least some > of them comes from calls the 'hostapd' process makes (I printed > current->comm in the warning). > > I am not having luck writing a simple script that reproduce this, > but my application that creates a VAP and bunch of virtual station > hits it every time on startup. > > Bryan: Do you have a simple script that reproduces this problem? > > Johannes: Any ideas on likely causes of this problem? Might help > me zero in on the problem quicker... Hm. Maybe this is the problem? http://p.sipsolutions.net/d432de678ae3ff17.txt johannes