| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 20 Apr 2009 00:49:09 +0200 From: Niel Lambrechts <niel.lambrechts@...il.com> To: "Rafael J. Wysocki" <rjw@...k.pl>, "linux.kernel" <linux-kernel@...r.kernel.org> Subject: Re: [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request 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 <maciej.rutecki@...il.com> >>> 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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists