Skip to contentSkip to conversation

iwl3945: wlan0: beacon loss from AP - sending probe request

Bug #13067 Niel Lambrechts 1 participant 2 messages Apr 19, 2009 – Apr 23, 2009 4 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#4 lore raw
Quoted 18 lines · Rafael J. Wysocki
Quoted 17 lines · Justin Madru
Quoted 16 lines · Rafael J. Wysocki

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 <[email protected]>
Date : 2009-04-05 9:11 (12 days old)
References : http://marc.info/?l=linux-kernel&m=123892272218266&w=4

Quoted 3 lines
Quoted 3 lines

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

#5 lore raw
Quoted 23 lines · Niel Lambrechts
Quoted 21 lines · Rafael J. Wysocki
Quoted 19 lines · Justin Madru
Quoted 17 lines · Rafael J. Wysocki

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 <[email protected]>
Date : 2009-04-05 9:11 (12 days old)
References : http://marc.info/?l=linux-kernel&m=123892272218266&w=4

Quoted 7 lines
Quoted 4 lines
Quoted 4 lines

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:

Just to let you know, this is still present in 2.6.30-rc3:

Apr 24 01:19:20 linux-7vph kernel: wlan0: beacon loss from AP
00:1d:92:1d:1e:8e - sending probe request
Apr 24 01:19:58 linux-7vph kernel: wlan0: beacon loss from AP
00:1d:92:1d:1e:8e - sending probe request
Apr 24 01:20:57 linux-7vph kernel: wlan0: beacon loss from AP
00:1d:92:1d:1e:8e - sending probe request
Apr 24 01:22:19 linux-7vph kernel: wlan0: beacon loss from AP

00:1d:92:1d:1e:8e - sending probe request

Niel