iwl4965: slow scans

iwl4965: slow scans

[Kyle McMartin]

Hi John,

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.

cheers, Kyle

Re: iwl4965: slow scans

[John W. Linville]

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?

John
-- 
John W. Linville
linville@tuxdriver.com

Re: iwl4965: slow scans

[Dan Williams]

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

Re: iwl4965: slow scans

[Kyle McMartin]

On Mon, Apr 21, 2008 at 02:02:56PM -0400, Dan Williams wrote:
> 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.
> 

I'm also poking the card with iwlist with NM off, and still see huge
delays waiting for the network to show up.

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

It's pretty invariant... disable_hw_scan=1 seems to be a bit faster, but
also breaks the second suspend, unless you unload the module first.

regards, Kyle