Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751751AbZDSWtm (ORCPT ); Sun, 19 Apr 2009 18:49:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750850AbZDSWtd (ORCPT ); Sun, 19 Apr 2009 18:49:33 -0400 Received: from mail-ew0-f176.google.com ([209.85.219.176]:63031 "EHLO mail-ew0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750814AbZDSWtc (ORCPT ); Sun, 19 Apr 2009 18:49:32 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=l3iipjrlcGr0kqvJKUjgn0LjxuWFiUVzbBE0SZgne+AONbf7OQZm1xyzXT+bs2iM2j /JQWiuhnk8xnWof+fepRBHO/xt6r82iXvavgVNrai+ex0wY8gHV4Zrlqlb+D8Zalg7FQ f5vjH5RqOuwho13KIe2BRm47T1JkNYkD1I9G8= Message-ID: <49EBAA65.80701@gmail.com> Date: Mon, 20 Apr 2009 00:49:09 +0200 From: Niel Lambrechts User-Agent: Thunderbird 2.0.0.21 (X11/20090310) MIME-Version: 1.0 To: "Rafael J. Wysocki" , "linux.kernel" Subject: Re: [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 5959 Lines: 158 On 04/17/2009 11:10 PM, Rafael J. Wysocki wrote: > On Friday 17 April 2009, Justin Madru wrote: >> Rafael J. Wysocki wrote: >>> This message has been generated automatically as a part of a report >>> of recent regressions. >>> >>> The following bug entry is on the current list of known regressions >>> from 2.6.29. Please verify if it still should be listed and let me know >>> (either way). >>> >>> >>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13067 >>> Subject : iwl3945: wlan0: beacon loss from AP - sending probe request >>> Submitter : Maciej Rutecki >>> Date : 2009-04-05 9:11 (12 days old) >>> References : http://marc.info/?l=linux-kernel&m=123892272218266&w=4 >>> >>> >>> >> I'm getting this on .30rc2, so I confirm that it's still an issue (I'm >> not the original submitter). >> It's really annoying because it's filling my logs like crazy. Below is Quite similar here, same kernel. I don't get this on 2.6.29 or 2.6.28: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 CPU0 attaching NULL sched-domain. CPU1 attaching NULL sched-domain. CPU0 attaching sched-domain: domain 0: span 0-1 level MC groups: 0 1 CPU1 attaching sched-domain: domain 0: span 0-1 level MC groups: 1 0 wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: beacon loss from AP 00:1d:92:1d:1e:8e - sending probe request wlan0: no probe response from AP 00:1d:92:1d:1e:8e - disassociating wlan0: authenticate with AP 00:1d:92:1d:1e:8e wlan0: authenticate with AP 00:1d:92:1d:1e:8e wlan0: authenticated wlan0: associate with AP 00:1d:92:1d:1e:8e wlan0: RX ReassocResp from 00:1d:92:1d:1e:8e (capab=0x411 status=0 aid=1) wlan0: associated Regards, Niel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/