[edgy] after a suspend to ram, ipw2200 module can't be reloaded

Bug #57697 reported by Nicolò Chieffo
6
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)
Invalid
Medium
Unassigned
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.15 (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.17

I'll try to be the most clear I can.
This bug is always reproduceble and it's very simple.

Every time I use the hotkey to switch off the wireless card (the hotkey is a shortcut to /etc/acpi/wireless.sh) the device is put into sleep by "echo -n 2 > $DEVICE/device/power/state".

if I do a suspend to ram after the wireless has been put to sleep, when I resume I get a failure:

Aug 25 13:44:44 yelo3-laptop kernel: [17179811.584000] ieee80211: 802.11 data/management/control stack, git-1.1.13
Aug 25 13:44:44 yelo3-laptop kernel: [17179811.584000] ieee80211: Copyright (C) 2004-2005 Intel Corporation <email address hidden>
Aug 25 13:44:44 yelo3-laptop kernel: [17179811.588000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.1.1
Aug 25 13:44:44 yelo3-laptop kernel: [17179811.588000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
Aug 25 13:44:44 yelo3-laptop kernel: [17179811.588000] Driver 'ipw2200' needs updating - please use bus_type methods
Aug 25 13:44:44 yelo3-laptop kernel: [17179811.604000] PCI: Enabling device 0000:02:02.0 (0000 -> 0002)
Aug 25 13:44:44 yelo3-laptop kernel: [17179811.604000] ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKB] -> GSI 4 (level, low) -> IRQ 4
Aug 25 13:44:44 yelo3-laptop kernel: [17179811.604000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Aug 25 13:44:44 yelo3-laptop kernel: [17179811.636000] ACPI: PCI interrupt for device 0000:02:02.0 disabled
Aug 25 13:44:44 yelo3-laptop kernel: [17179811.636000] ipw2200: probe of 0000:02:02.0 failed with error -5

if the wireless device is in normal state this problem won't occur.
This bug can be solved whitelisting the ipw2200 module, so that it is not unloaded during a suspension!

Tags: edgy-close
Revision history for this message
Simon Law (sfllaw) wrote :

A workaround has been proposed.

Changed in acpi-support:
importance: Untriaged → Medium
status: Unconfirmed → Confirmed
Changed in linux-source-2.6.17:
status: Unconfirmed → Rejected
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

What type of workaround?

Revision history for this message
Simon Law (sfllaw) wrote :

By this, I mean that if acpi-support whitelisted the ipw2200, as you had proposed, then this would work.

Revision history for this message
Nicolò Chieffo (yelo3) wrote : Re: [Bug 57697] Re: [edgy] after a suspend to ram, ipw2200 module can't be reloaded

Ok, thank you for the reply!

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

In Feisty even if the wireless is deactivated, after the suspend the module is loaded (I don't think it has been put to whitelist) so this bug is fixed. Unfortunately the wireless becomes enabled and can't no more be disabled. I will open a new bug

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

this bug is not fixed, sorry. in feisty is no more possible to disable wireless using the power/state file.I don't know why, but whenever I try to write that file I get an I/O error

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

closing the bug since the possibility to use the file power/state is now deprecated.
feisty linux-2.6.20

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

deprecated usage

Changed in acpi-support:
status: Confirmed → Rejected
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

reopening since this is an edgy package

Changed in linux-source-2.6.17:
status: Rejected → Confirmed
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

reopening because it is a dapper package

Changed in linux-source-2.6.15:
status: Unconfirmed → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.17:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

OK, but I cannot help you anymore since I'm not using dapper

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, please note that this report will remain open against the actively developed kernel. Thank you for your continued support and help as we debug this issue.

Changed in linux-source-2.6.17:
status: Confirmed → Invalid
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

This bug is only in dapper

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

@Nicolò

You can confirm it is fixed in Hardy?

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

It's fixed in kernel 2.6.20 so if I remember well, since feisty

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Ok, so I put it as fixed.
Thanks.

Changed in linux:
status: Incomplete → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Thank you for reporting this bug to Ubuntu. Dapper reached EOL, please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Feel free to report any other bugs you may find.

Changed in linux-source-2.6.15 (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.