Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>, linux-wireless@vger.kernel.org
Subject: Re: iwl4965: slow scans
Date: Mon, 21 Apr 2008 14:02:56 -0400	[thread overview]
Message-ID: <1208800976.32409.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20080421174122.GA10857@tuxdriver.com>

On Mon, 2008-04-21 at 13:41 -0400, John W. Linville wrote:
> On Mon, Apr 21, 2008 at 12:03:18PM -0400, Kyle McMartin wrote:
> 
> > I've noticed recently in rawhide that scanning for networks when I come
> > back from suspend takes an age. It seems to be upwards of 3~4 minutes
> > before I'm able to reassociate with my ap.
> > 
> > I'm pulling a pile of rpms to figure out when the change to
> > linux-2.6-wireless*.patch might have caused this (it doesn't *seem* to
> > happen on upstream, but since the patch might make it to upstream soon,
> > I figured I should keep linux-wireless@ in the loop.)
> > 
> > Willing to bash on whatever I need to to improve this.
> 
> Sounds like the issue here:
> 
> 	https://bugzilla.redhat.com/show_bug.cgi?id=441819
> 
> Perhaps you could post some iwevent info as Dan requested there as well?

Yeah, could be an NM issue or a supplicant issue I guess.  Or, even if
the card _is_ returning scan results, it might not be returning results
for your AP.

Do you have hardware or software scanning on (ie, is disable_hw_scan
module option 1 or 0?)

dan


  reply	other threads:[~2008-04-21 18:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21 16:03 iwl4965: slow scans Kyle McMartin
2008-04-21 17:41 ` John W. Linville
2008-04-21 18:02   ` Dan Williams [this message]
2008-04-21 18:49     ` Kyle McMartin

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=1208800976.32409.0.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=kyle@mcmartin.ca \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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