iwl3945 losing association after resume from suspend

iwl3945 losing association after resume from suspend

[Andrey Borzenkov]

[-- Attachment #1: Type: Text/Plain, Size: 329 bytes --]

I am running 2.6.29.3. After resume from STR (assuming that long enough 
time has passed) connectivity is lost. There is no messages in log. Just 
running "wpa_cli reassociate" "fixes" it.

Is there any way driver can declare existing connection as "stale" and 
tell wpa_supplicant to reassociate?

Thank you!

-andrey

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: iwl3945 losing association after resume from suspend

[Dan Williams]

On Tue, 2009-05-26 at 20:51 +0400, Andrey Borzenkov wrote:
> I am running 2.6.29.3. After resume from STR (assuming that long enough 
> time has passed) connectivity is lost. There is no messages in log. Just 
> running "wpa_cli reassociate" "fixes" it.
> 
> Is there any way driver can declare existing connection as "stale" and 
> tell wpa_supplicant to reassociate?

Send a disassociate event on resume if a few seconds have passed.  But
in reality, this is usually done in userspace via pm-utils
suspend/resume scripts or some other mechanism based on the kernel's
uevents.  It's not something that kernel drivers report back to
userspace, because that suspend/resume event is handled by the kernel in
a non-driver-specific fashion.  You could use pm-utils scripts to
trigger the reassociation if you like, which is where most of the
userspace suspend/resume handling stuff lives these days.

Dan