wireless interface inactive after Suspend

[Chris Conway]

Binary package hint: network-manager

network-manager version 0.6.3-2ubuntu6 (edgy)
linux-image-2.6.17-10-generic version 2.6.17.1-10.34

Every now and then, when I come back from suspend, the wireless connection (driver ipw3945) is not re-activated. The radio indicator isn't lit and "Enable Wireless" does not appear in the applet menu. Removing and re-starting the driver module succeeds in re-activating the interface. I.e.,

rmmod ipw3945
modprobe ipw3945

The radio indicator flickers back on, the "Enable Wireless" option comes back (already selected), and the interface comes up.

Here's the wireless adapter info from lspci:
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

[Scott Robinson (scott-ubuntu)]

This is a bug in acpi-support, and not in network-manger. NM doesn't have anything to do with loading modules.

The issue appears to be that the module (or the regulatory daemon) doesn't properly support suspend. Perhaps adding it to the suspend blacklist might help?

[Chris Conway (cconway)]

RE: This bug being a duplicate, I would note that I am not having problems with boot/reboot at all. The problem is only with the module not loading on resume after suspend.

This only pops up intermittently, so I haven't had a chance to try any suggested solutions yet. Can someone post a more specific pointer to the "suspend blacklist". Google is utterly failing me on that. There's no mention in the marked duplicate bug, either.

[Chris Conway (cconway)]

Since this has be re-assigned to acpi-support, I'll add:
acpi-support version 0.90
acpid version 1.0.4-5ubuntu4

[Chris Conway (cconway)]

Pressing the "wireless kill" key after Resume doesn't help.

[Leann Ogasawara (leannogasawara)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out, we were wondering if you can still reproduce this issue. Could you please download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download and report back your results. If the issue is still present in the new release, please attach the following information:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Please be sure to attach each file as a separate attachment. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[wolfger (wolfger)]

6 months without a response. Also wondering why there is no longer the duplicate mentioned over a year ago. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Chris Conway (cconway)]

This has not been an issue for me in quite some time. I apologize for not updating the bug status.