Bug 695 – Suspend to ram/disk cannot reassociate to AP

Bug 695 - Suspend to ram/disk cannot reassociate to AP

Summary:

Suspend to ram/disk cannot reassociate to AP

Status:	VERIFIED FIXED

Product:	IPW2200
Component:	Power Management
Version:	1.0.4
Platform:	IBM Debian

Importance:	P2 normal
Assigned To:	Zhu Yi
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-06-09 22:49 by Shawn Starr
Modified:	2005-07-20 14:34 (History)

Attachments
fix hw key reset on resume (999 bytes, patch) 2005-06-13 03:01, Zhu Yi	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Shawn Starr 2005-06-09 22:49:22

With 1.0.4, I am not able to properly reassociate with my AP when resuming from 
a suspend to ram or to disk. 
 
I have to force the reassociation. 
 
[4576515.871000] PCI: Setting latency timer of device 0000:00:1f.5 to 64 
[4576515.927000] ipw2200: failed to send SCAN_REQUEST_EXT command 
[4576516.946000] ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNKA] -> GSI 9 
(level, low) -> IRQ 9 
[4576516.971000] eth1: Coming out of suspend... 
[4576516.982000] ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI 10 
(level, low) -> IRQ 10 
[4576517.321000] uhci_hcd 0000:00:1d.2: suspend_hc 
[4576517.321000] uhci_hcd 0000:00:1d.1: suspend_hc 
[4576517.321000] uhci_hcd 0000:00:1d.0: suspend_hc 
[4576517.437000] ieee80211: eth1: Unknown management packet: 0

------- Comment #1 From Shawn Starr 2005-06-09 22:49:44 -------

Kernel is: 2.6.12-rc5. Have not tried -rc6 yet.

------- Comment #2 From Zhu Yi 2005-06-09 23:15:14 -------

Are you using open or encryption? Please provide dmesg for debug level 255.

------- Comment #3 From Zhu Yi 2005-06-13 03:01:56 -------

Created an attachment (id=422) [details]
fix hw key reset on resume

------- Comment #4 From Zhu Yi 2005-06-13 03:03:04 -------

mark as fixed

------- Comment #5 From Salwan Searty 2005-07-14 11:43:00 -------

Hi Shawn,
Has this been resolved for you in version 1.0.5 or later?

------- Comment #6 From Shawn Starr 2005-07-14 13:00:51 -------

Should be testing this tonight, but have been having issues with git <->
2.6.13-rcX as such...

------- Comment #7 From Shawn Starr 2005-07-20 11:05:11 -------

Yes, this is fixed in 1.0.6. 
 
Please close.

------- Comment #8 From Salwan Searty 2005-07-20 14:34:41 -------

Marking as verified, per submitter's last comment.