Bugzilla – Bug 363
ACPI S4 wakeup problem
Last modified: 2005-10-03 14:36:25
You need to log in before you can comment on or make changes to this bug.
After wakeup from Suspend-to-disk (S4) driver doesn't restart itself. Here debug output. wlan0: Coming out of suspend... ipw2200: U ipw_load initial device response after 20ms ipw2200: U ipw_stop_master stop master 0ms ipw2200: U ipw_load_ucode Microcode OK, rev. 53310 (0xd03e) dev. 3 (0x3) of 05/15/04 06:46 ipw2200: U ipw_load device response after 130ms ipw2200: U ipw_eeprom_init_sram Writing EEPROM data into SRAM ipw2200: U ipw_send_cmd Sending TX_POWER command (#35), 76 bytes 00000000 0B 02 01 14 02 14 03 14 04 14 05 14 06 14 07 14 ........ ........ 00000010 08 14 09 14 0A 14 0B 14 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000040 00 00 00 00 00 00 00 00 00 00 00 00 ........ .... ipw2200: U ipw_send_cmd Command completion failed out after 100ms. ipw2200: failed to send TX_POWER command ipw2200: U ipw_up Device configuration failed: 0xFFFFFFFB ipw2200: U ipw_up Failed to config device on retry 0 of 5 ipw2200: U ipw_load initial device response after 20ms ipw2200: U ipw_stop_master stop master 0ms ipw2200: U ipw_load_ucode Microcode OK, rev. 53310 (0xd03e) dev. 3 (0x3) of 05/15/04 06:46 ipw2200: U ipw_load device response after 130ms ipw2200: U ipw_eeprom_init_sram Writing EEPROM data into SRAM ipw2200: U ipw_send_cmd Sending TX_POWER command (#35), 76 bytes 00000000 0B 02 01 14 02 14 03 14 04 14 05 14 06 14 07 14 ........ ........ 00000010 08 14 09 14 0A 14 0B 14 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000040 00 00 00 00 00 00 00 00 00 00 00 00 ........ .... ipw2200: U ipw_send_cmd Command completion failed out after 100ms. ipw2200: failed to send TX_POWER command ipw2200: U ipw_up Device configuration failed: 0xFFFFFFFB ipw2200: U ipw_up Failed to config device on retry 1 of 5 ipw2200: U ipw_load initial device response after 20ms ipw2200: U ipw_stop_master stop master 0ms ipw2200: U ipw_load_ucode Microcode OK, rev. 53310 (0xd03e) dev. 3 (0x3) of 05/15/04 06:46 ipw2200: U ipw_load device response after 130ms ipw2200: U ipw_eeprom_init_sram Writing EEPROM data into SRAM ipw2200: U ipw_send_cmd Sending TX_POWER command (#35), 76 bytes 00000000 0B 02 01 14 02 14 03 14 04 14 05 14 06 14 07 14 ........ ........ 00000010 08 14 09 14 0A 14 0B 14 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000040 00 00 00 00 00 00 00 00 00 00 00 00 ........ .... ipw2200: U ipw_send_cmd Command completion failed out after 100ms. ipw2200: failed to send TX_POWER command ipw2200: U ipw_up Device configuration failed: 0xFFFFFFFB ipw2200: U ipw_up Failed to config device on retry 2 of 5 ipw2200: U ipw_load initial device response after 20ms ipw2200: U ipw_stop_master stop master 0ms ipw2200: U ipw_load_ucode Microcode OK, rev. 53310 (0xd03e) dev. 3 (0x3) of 05/15/04 06:46 ipw2200: U ipw_load device response after 130ms ipw2200: U ipw_eeprom_init_sram Writing EEPROM data into SRAM ipw2200: U ipw_send_cmd Sending TX_POWER command (#35), 76 bytes 00000000 0B 02 01 14 02 14 03 14 04 14 05 14 06 14 07 14 ........ ........ 00000010 08 14 09 14 0A 14 0B 14 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000040 00 00 00 00 00 00 00 00 00 00 00 00 ........ .... ipw2200: U ipw_send_cmd Command completion failed out after 100ms. ipw2200: failed to send TX_POWER command ipw2200: U ipw_up Device configuration failed: 0xFFFFFFFB ipw2200: U ipw_up Failed to config device on retry 3 of 5 ipw2200: U ipw_load initial device response after 20ms ipw2200: U ipw_stop_master stop master 0ms ipw2200: U ipw_load_ucode Microcode OK, rev. 53310 (0xd03e) dev. 3 (0x3) of 05/15/04 06:46 ipw2200: U ipw_load device response after 130ms ipw2200: U ipw_eeprom_init_sram Writing EEPROM data into SRAM ipw2200: U ipw_send_cmd Sending TX_POWER command (#35), 76 bytes 00000000 0B 02 01 14 02 14 03 14 04 14 05 14 06 14 07 14 ........ ........ 00000010 08 14 09 14 0A 14 0B 14 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000040 00 00 00 00 00 00 00 00 00 00 00 00 ........ .... ipw2200: U ipw_send_cmd Command completion failed out after 100ms. ipw2200: failed to send TX_POWER command ipw2200: U ipw_up Device configuration failed: 0xFFFFFFFB ipw2200: U ipw_up Failed to config device on retry 4 of 5 ipw2200: Unable to initialize device after 5 attempts. After removing module and reloading it everything works fine, so it can't be a hardware issue. Looks like some initialization part needs to be done also after coming from suspend. -- Cougar
What's your kernel version?
This is SuSE 9.2 kernel 2.6.8-24.3-default. It based on 2.6.8 but should have a lot of patches includes (SuSE does it always..) Btw, before I couldn't test Suspend-to-RAM (S3) but now I found the problem (was USB retated thing). Tested it and IPW2200 works fine with S3.
This should be a upstream kernel(ACPI) bug. I can reproduce it on vanilla 2.6.9, 2.6.9-mm1 and 2.6.10-rc but not 2.6.8.1. Can you verify kernels before 2.6.8.1 works for you?
Created an attachment (id=102) [details] fix / workaround no fail init in resume This patch should make resume work even if no interrupt during resume. Please verify.
You were right. With SuSE 9.1 kernel 2.6.5-7.111-default it worked fine. Your patch works fine with 2.6.8-24.3-default also. Thanks!
Created an attachment (id=111) [details] 2.6.10-rc2 kernel fix This patch fixed the upstream kernel swsusp bug. System devices (i.e. PCI link device) should be suspend and resume as well.
This is an ACPI bug. Only a workaround patch in ipw2200 source code. Users can use the patch to avoid the problem. (But the patch should not be put in ipw2200 driver, right?) Mark the bug as verified.
James feels free to integrate attachment 102 [details]. No big win for a sanity kernel except it is faster during resume then now.
*** Bug 444 has been marked as a duplicate of this bug. ***
Since 0.19 this problem is gone and manual patch is not needed any more. Thanks for everyone who helped -- Cougar
Per comment #8, applied attachment 102 [details] for 0.20
Is the kernel patch still needed with kernel 2.6.10? I (sometimes) still get the TX_POWER errors. Putting the notebook to sleep (S3) and waking it up fixes the problem though. I am running ipw2200-0.21 on a IBM Thinkpad X40 with kernel 2.6.10. Running 'modprobe ipw2200 debug=0xffff' dumps this a couple times to dmesg: ipw2200: Copyright(c) 2003-2004 Intel Corporation ACPI: PCI interrupt 0000:02:02.0[A] -> GSI 11 (level, low) -> IRQ 11 ipw2200: U ipw_pci_probe pci_resource_len = 0x00001000 ipw2200: U ipw_pci_probe pci_resource_base = e018c000 ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: U ipw_get_fw Loading firmware 'ipw-2.2-boot.fw' file v2.0 (6464 bytes) ipw2200: U ipw_get_fw Loading firmware 'ipw-2.2-bss_ucode.fw' file v2.0 (16326 bytes) ipw2200: U ipw_get_fw Loading firmware 'ipw-2.2-bss.fw' file v2.0 (166952 bytes) ipw2200: U ipw_load initial device response after 10ms ipw2200: U ipw_stop_master stop master 0ms ipw2200: U ipw_load_ucode Microcode OK, rev. 53594 (0xd15a) dev. 3 (0x3) of 11/22/04 20:27 ipw2200: U ipw_load device response after 50ms ipw2200: U ipw_eeprom_init_sram Writing EEPROM data into SRAM ipw2200: U ipw_send_cmd Sending TX_POWER command (#35), 76 bytes 00000000 0B 02 01 14 02 14 03 14 04 14 05 14 06 14 07 14 ........ ........ 00000010 08 14 09 14 0A 14 0B 14 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000040 00 00 00 00 00 00 00 00 00 00 00 00 ........ .... ipw2200: U ipw_send_cmd Command completion failed out after 1000ms. ipw2200: failed to send TX_POWER command ipw2200: U ipw_up Device configuration failed: 0xFFFFFFFB ipw2200: U ipw_up Failed to config device on retry 0 of 5
2.6.10 still need this patch. 2.6.11-rc1 and -mm will be fine.