Bug 902664

Summary:	iwl4965 doesn't realise it has lost association after suspend [regression]
Product:	[Fedora] Fedora	Reporter:	Pierre Ossman <pierre-bugzilla>
Component:	kernel	Assignee:	Stanislaw Gruszka <sgruszka>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, schaiba, sgruszka
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-29 14:00:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***