From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from fk-out-0910.google.com ([209.85.128.185]:35146 "EHLO fk-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753174AbZDFI4i (ORCPT ); Mon, 6 Apr 2009 04:56:38 -0400 From: Helmut Schaa To: Kalle Valo Subject: Re: ath9k becon loss messages Date: Mon, 6 Apr 2009 10:56:27 +0200 Cc: Jaswinder Singh Rajput , Michael Buesch , Sujith , wireless , David Miller , LKML References: <1238923439.4120.9.camel@localhost.localdomain> <200904060914.32245.helmut.schaa@gmail.com> <873acmyz4x.fsf@litku.valot.fi> In-Reply-To: <873acmyz4x.fsf@litku.valot.fi> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-Id: <200904061056.28495.helmut.schaa@gmail.com> (sfid-20090406_105642_461928_B196C218) Sender: linux-wireless-owner@vger.kernel.org List-ID: Am Montag, 6. April 2009 schrieb Kalle Valo: > Helmut Schaa writes: > > >> Then there is something happening in ath9k or your AP which prevents > >> ath9k from receiving beacons. Try pinging your AP with 100 ms > >> interval. Do you see anything happening in 120 s intervals? > > > > NetworkManager typically scans every 120 seconds and I can also trigger > > the messages by a manual scan with iwlist. I did not dig any further but > > the messages seem to appear right at the end of the scan. Tried with iwlagn > > and both sw_scan and hw_scan. > > Thanks, this was valuable info. It might be that my beacon filtering > patches broke something related to scanning and beacon loss check. I'll > take a look at this. Maybe you did not break anything. During a scan we will stay away from the operating channel for some seconds which indeed prevents us from receiving beacons. I'd say sending a probe request to the AP in that case won't hurt. Helmut