Bug 902664 - iwl4965 doesn't realise it has lost association after suspend [regression]
Summary: iwl4965 doesn't realise it has lost association after suspend [regression]
Keywords:
Status: CLOSED DUPLICATE of bug 893580
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stanislaw Gruszka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-22 08:00 UTC by Pierre Ossman
Modified: 2013-01-29 14:00 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-29 14:00:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Pierre Ossman 2013-01-22 08:00:06 UTC 
This is a regression since Fedora 17.

When I suspend my machine, move to a new location, and resume again, it now takes forever before the machine realises it cannot talk to the old AP and needs to find a new one. Often I have to manually force a change.
Comment 1 Stanislaw Gruszka 2013-01-24 13:16:36 UTC 
Basically what we do on suspend is remove the interface (i.e. wlan0) and create it again on resume. So I'm not sure where the problem came from, seems like NetworkManager issue. I'll try to reproduce problem locally and see what is wrong.
Comment 2 Stanislaw Gruszka 2013-01-29 14:00:07 UTC 

*** This bug has been marked as a duplicate of bug 893580 ***
Note You need to log in before you can comment on or make changes to this bug.