Wifi driver fixes for age scan
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Fedora) |
Fix Released
|
Low
|
|||
linux (Ubuntu) |
Fix Released
|
Low
|
Tim Gardner | ||
Jaunty |
Fix Released
|
Low
|
Tim Gardner | ||
pm-utils (Ubuntu) |
Fix Released
|
Medium
|
Steve Langasek | ||
Jaunty |
Fix Released
|
Medium
|
Steve Langasek |
Bug Description
SRU justification:
Impact: The houskeeping of the wireless stack does not account for the time spent in suspend. So after resume it will think the AP's from the last scan are still valid and tries to reconnect to the one connected to before suspended.
Fix: Account for the time spent in suspend when resuming. Patch taken from https:/
Testcase: Connect to an access point, suspend, move away and resume.
---
When you resume from suspend the wifi drivers get confused and network-manager continues to show the access points from when you suspended the laptop. Dan Williams has fixes for this.
Changed in linux: | |
status: | Unknown → Fix Committed |
Changed in linux: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux (Fedora): | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu Jaunty): | |
milestone: | ubuntu-9.04-beta → ubuntu-9.04 |
Changed in pm-utils (Ubuntu Jaunty): | |
assignee: | nobody → vorlon |
importance: | Undecided → Medium |
milestone: | none → ubuntu-9.04 |
status: | New → Confirmed |
Changed in pm-utils (Ubuntu Jaunty): | |
status: | Confirmed → In Progress |
Changed in linux (Ubuntu Jaunty): | |
milestone: | ubuntu-9.04 → none |
Changed in linux (Ubuntu Jaunty): | |
status: | Confirmed → In Progress |
description: | updated |
Changed in linux (Ubuntu Jaunty): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu): | |
assignee: | Tim Gardner (timg-tpi) → vikaspandole (vikaspandole) |
Changed in linux (Ubuntu): | |
assignee: | vikaspandole (vikaspandole) → Tim Gardner (timg-tpi) |
Changed in linux (Fedora): | |
importance: | Unknown → Low |
Description of problem:
I regularly use my laptop with two wireless networks in different locations. When I suspend the laptop while it is connected to network "A," then resume it within the range of network "B," NetworkManager usually made an immediate connection to network "B."
With the latest update, NetworkManager instead attempts to connect to network "A," which is over 10 miles away. Failing at this, it will prompt me for network secrets; clicking "Cancel" in this dialog box will cause it to connect to network "B" as was previously its practice.
Version-Release number of selected component (if applicable):
NetworkManager version: 0.7.0-0. 11.svn4022. 4.fc9.x86_ 64
Wireless driver: iwl3945