* [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request
2009-04-16 21:42 2.6.30-rc2-git2: Reported regressions from 2.6.29 Rafael J. Wysocki
@ 2009-04-16 21:45 ` Rafael J. Wysocki
2009-04-17 3:38 ` Justin Madru
0 siblings, 1 reply; 6+ messages in thread
From: Rafael J. Wysocki @ 2009-04-16 21:45 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Maciej Rutecki
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@gmail.com>
Date : 2009-04-05 9:11 (12 days old)
References : http://marc.info/?l=linux-kernel&m=123892272218266&w=4
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request
2009-04-16 21:45 ` [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request Rafael J. Wysocki
@ 2009-04-17 3:38 ` Justin Madru
2009-04-17 21:09 ` Rafael J. Wysocki
0 siblings, 1 reply; 6+ messages in thread
From: Justin Madru @ 2009-04-17 3:38 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki
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@gmail.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
15mins of logs, and it just repeats like this.
dhclient: DHCPREQUEST of 192.168.1.5 on wlan0 to 192.168.1.254 port 67
dhclient: DHCPACK of 192.168.1.5 from 192.168.1.254
dhclient: bound to 192.168.1.5 -- renewal in 823 seconds.
NetworkManager: <debug> [1239937333.003788] periodic_update(): Roamed
from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
NetworkManager: <debug> [1239937339.001004] periodic_update(): Roamed
from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
NetworkManager: <debug> [1239937453.002911] periodic_update(): Roamed
from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
NetworkManager: <debug> [1239937459.000974] periodic_update(): Roamed
from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
NetworkManager: <debug> [1239937573.002956] periodic_update(): Roamed
from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
NetworkManager: <debug> [1239937579.000971] periodic_update(): Roamed
from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
NetworkManager: <debug> [1239937693.003787] periodic_update(): Roamed
from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
NetworkManager: <debug> [1239937699.000981] periodic_update(): Roamed
from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
NetworkManager: <debug> [1239937813.002710] periodic_update(): Roamed
from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
NetworkManager: <debug> [1239937819.000753] periodic_update(): Roamed
from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
NetworkManager: <debug> [1239937933.003806] periodic_update(): Roamed
from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
NetworkManager: <debug> [1239937939.000724] periodic_update(): Roamed
from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
NetworkManager: <debug> [1239938053.002711] periodic_update(): Roamed
from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
NetworkManager: <debug> [1239938059.001749] periodic_update(): Roamed
from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
dhclient: DHCPREQUEST of 192.168.1.5 on wlan0 to 192.168.1.254 port 67
dhclient: DHCPACK of 192.168.1.5 from 192.168.1.254
dhclient: bound to 192.168.1.5 -- renewal in 803 seconds.
Justin Madru
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request
2009-04-17 3:38 ` Justin Madru
@ 2009-04-17 21:09 ` Rafael J. Wysocki
0 siblings, 0 replies; 6+ messages in thread
From: Rafael J. Wysocki @ 2009-04-17 21:09 UTC (permalink / raw)
To: Justin Madru
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki
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@gmail.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
> 15mins of logs, and it just repeats like this.
>
> dhclient: DHCPREQUEST of 192.168.1.5 on wlan0 to 192.168.1.254 port 67
> dhclient: DHCPACK of 192.168.1.5 from 192.168.1.254
> dhclient: bound to 192.168.1.5 -- renewal in 823 seconds.
> NetworkManager: <debug> [1239937333.003788] periodic_update(): Roamed
> from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
> kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
> NetworkManager: <debug> [1239937339.001004] periodic_update(): Roamed
> from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
> NetworkManager: <debug> [1239937453.002911] periodic_update(): Roamed
> from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
> kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
> NetworkManager: <debug> [1239937459.000974] periodic_update(): Roamed
> from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
> NetworkManager: <debug> [1239937573.002956] periodic_update(): Roamed
> from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
> kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
> NetworkManager: <debug> [1239937579.000971] periodic_update(): Roamed
> from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
> NetworkManager: <debug> [1239937693.003787] periodic_update(): Roamed
> from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
> kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
> NetworkManager: <debug> [1239937699.000981] periodic_update(): Roamed
> from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
> NetworkManager: <debug> [1239937813.002710] periodic_update(): Roamed
> from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
> kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
> NetworkManager: <debug> [1239937819.000753] periodic_update(): Roamed
> from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
> NetworkManager: <debug> [1239937933.003806] periodic_update(): Roamed
> from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
> kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
> NetworkManager: <debug> [1239937939.000724] periodic_update(): Roamed
> from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
> NetworkManager: <debug> [1239938053.002711] periodic_update(): Roamed
> from BSSID 00:1C:DF:67:1F:AC (madru) to (none) ((none))
> kernel: wlan0: beacon loss from AP 00:1c:df:67:1f:ac - sending probe request
> NetworkManager: <debug> [1239938059.001749] periodic_update(): Roamed
> from BSSID (none) ((none)) to 00:1C:DF:67:1F:AC (madru)
> dhclient: DHCPREQUEST of 192.168.1.5 on wlan0 to 192.168.1.254 port 67
> dhclient: DHCPACK of 192.168.1.5 from 192.168.1.254
> dhclient: bound to 192.168.1.5 -- renewal in 803 seconds.
Thanks for the update.
Rafael
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request
[not found] ` <cs3u2-7kZ-13@gated-at.bofh.it>
@ 2009-04-19 22:49 ` Niel Lambrechts
2009-04-23 23:23 ` Niel Lambrechts
0 siblings, 1 reply; 6+ messages in thread
From: Niel Lambrechts @ 2009-04-19 22:49 UTC (permalink / raw)
To: Rafael J. Wysocki, linux.kernel
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@gmail.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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request
2009-04-19 22:49 ` [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request Niel Lambrechts
@ 2009-04-23 23:23 ` Niel Lambrechts
0 siblings, 0 replies; 6+ messages in thread
From: Niel Lambrechts @ 2009-04-23 23:23 UTC (permalink / raw)
To: Rafael J. Wysocki, linux.kernel
On 04/20/2009 12:49 AM, Niel Lambrechts wrote:
> 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@gmail.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:
>
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request
2009-04-25 19:22 2.6.30-rc3-git1: Reported regressions from 2.6.29 Rafael J. Wysocki
@ 2009-04-25 19:31 ` Rafael J. Wysocki
0 siblings, 0 replies; 6+ messages in thread
From: Rafael J. Wysocki @ 2009-04-25 19:31 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Maciej Rutecki
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@gmail.com>
Date : 2009-04-05 9:11 (21 days old)
References : http://marc.info/?l=linux-kernel&m=123892272218266&w=4
Patch : http://bugzilla.kernel.org/show_bug.cgi?id=13067#c6
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-04-25 22:18 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <crKhD-25m-3@gated-at.bofh.it>
[not found] ` <crKhG-25m-5@gated-at.bofh.it>
[not found] ` <crN5T-6s8-5@gated-at.bofh.it>
[not found] ` <cs3u2-7kZ-13@gated-at.bofh.it>
2009-04-19 22:49 ` [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request Niel Lambrechts
2009-04-23 23:23 ` Niel Lambrechts
2009-04-25 19:22 2.6.30-rc3-git1: Reported regressions from 2.6.29 Rafael J. Wysocki
2009-04-25 19:31 ` [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2009-04-16 21:42 2.6.30-rc2-git2: Reported regressions from 2.6.29 Rafael J. Wysocki
2009-04-16 21:45 ` [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request Rafael J. Wysocki
2009-04-17 3:38 ` Justin Madru
2009-04-17 21:09 ` Rafael J. Wysocki
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).