linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Niel Lambrechts <niel.lambrechts@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>,
	"linux.kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [Bug #13067] iwl3945: wlan0: beacon loss from AP - sending probe request
Date: Fri, 24 Apr 2009 01:23:34 +0200	[thread overview]
Message-ID: <49F0F876.7090402@gmail.com> (raw)
In-Reply-To: <49EBAA65.80701@gmail.com>

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


  reply	other threads:[~2009-04-23 23:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49F0F876.7090402@gmail.com \
    --to=niel.lambrechts@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).