iwl4965 does not work after resume

[Björn Torkelsson]

After resuming, from suspend, my T61 with a Intel 4965AGN the wireless does not come back.

Output from dmesg:

[ 1.640952] iwl4965: MAC is in deep sleep!
[ 1.691145] iwl4965: MAC is in deep sleep!
[ 1.741412] iwl4965: MAC is in deep sleep!
[ 1.791635] iwl4965: MAC is in deep sleep!
[ 1.791645] iwl4965: Unable to int nic

I have also tried to remove the iw4965 module and modprobing it. But it still says it is in deep sleep. From syslog:

Sep 28 08:11:22 skruttibangbang kernel: [ 180.703944] iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.0
Sep 28 08:11:22 skruttibangbang kernel: [ 180.703953] iwl4965: Copyright(c) 2003-2007 Intel Corporation
Sep 28 08:11:22 skruttibangbang kernel: [ 180.705474] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Sep 28 08:11:22 skruttibangbang kernel: [ 180.705526] PCI: Setting latency timer of device 0000:03:00.0 to 64
Sep 28 08:11:22 skruttibangbang kernel: [ 180.708325] iwl4965: Detected Intel Wireless WiFi Link 4965AGN
Sep 28 08:11:22 skruttibangbang kernel: [ 180.822771] iwl4965: MAC is in deep sleep!
Sep 28 08:11:22 skruttibangbang kernel: [ 180.822800] iwl4965: Unable to int nic

It does come back when resuming from hibernation. though.

[Olivier Cortès (olive)]

Here on a Dell Precision M4300, iwl4965 works after a suspend/resume cycle. dmesg says nothing particular about the card, but network-manager says "no network adapter detected" (it does not even detect the wired ethernet device, but that's another bug, i will search/report elsewhere).
"iwconfig" shows the iwl4965, and manually associating the card with my AP works (with "iwconfig wlan0 essid ... enc s:..."). Anyway if you need more testing for positive or negative results about this bug, I subscribe to it.
regards,

[tuxo (beat-fasel)]

I have the same problem as the original poster. Up-to-date Gutsy Gibbon. I can suspend, however, upon wake up, the wireless does not come back and I have to reboot. My Laptop is a Littlebit (ASUS) with an intel 4965 AG or AGN network controller (rev 61). Platform: Santa Rosa.

[tuxo (beat-fasel)]

I investigated unloading network modules prior and reloading after a suspend operation. Hereby, I modified following file:

/etc/default/acpi-support

and added iwl4965 iwlwifi_mac80211 cfg80211 to the MODULES part:

MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

With this, I managed to get the wireless working after a suspend operation. However, it worked only once. The many other times I tried, the network was frozen after suspend anyway.

I hope that a solution can be found for this problem and updated driver will be backported soon for Gutsy Gibbon.

For now I am back to using ndiswrapper that works mostly. However, it gave me occasional freezes and often CPU softlocks during booting in the past. So this is not a solution either.

[Tim Gardner (timg-tpi)]

Try iwlwifi 1.2.0 according to instructions in https://bugs.edge.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/144621

[geppz (no-carrier)]

It might be this bug: (symptoms are similar though not exactly identical)
http://bughost.org/bugzilla/show_bug.cgi?id=1539
which has just been fixed with a patch as you can see from the discussion there.

You can apply the patch to the iwlwifi-1.2.22.tgz sources then compile and install.
Please see the following thread suggested by Tim Gardner which has more detailed instruction for recompiling the intellinuxwireless
https://bugs.edge.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/144621
I will add my comment also there

This bugfix should really be included in the modules update due at the end of the year please.

[John Karp (johnkarp)]

I'm experiencing this with up-to-date Hardy. Has the fix gotten out yet?

T61/iwl4965 1.2.0/2.6.24-19-generic/"Unable to int nic"

[tuxo (beat-fasel)]

It works for me with up-to-date Hardy.

My network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)

Kernel: 2.6.24-19-generic

----- Original Message ----
> From: John Karp <email address hidden>
> To: <email address hidden>
> Sent: Sunday, June 22, 2008 7:27:42 AM
> Subject: [Bug 146191] Re: iwl4965 does not work after resume
>
> I'm experiencing this with up-to-date Hardy. Has the fix gotten out yet?
>
> T61/iwl4965 1.2.0/2.6.24-19-generic/"Unable to int nic"
>
> --
> iwl4965 does not work after resume
> https://bugs.launchpad.net/bugs/146191
> You received this bug notification because you are a direct subscriber
> of the bug.

[Leann Ogasawara (leannogasawara)]

Hi John,

Sorry for the delayed response here. Care to maybe open a new bug report regarding the issue you are seeing? Even though you are using the same driver and are experiencing the same symptom of this bug report, after examining your dmesg output it seems the errors you are seeing are quite different than what was originally reported here. It's just helpful to the development teams if bug reports target a specific issue against a specific set of hardware.

Additionally, it would be great if you would be willing to test the latest Alpha for the upcoming Intrepid Ibex 8.10 release since it is actively being worked on. You should be able to test via a LiveCD (note you can only test Suspend via the LiveCD, not hibernate) - http://www.ubuntu.com/testing. Please let us know your results. If the issue still exists, per the kernel team's bug policy, can you please attach the following information in your new bug report. Please be sure to attach each file as a separate attachment.

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

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies .

Also, if you could open your new bug report against the "linux" package that would be great. Beginning with the Intrepid development cycle, the linux-ubuntu-modules package was merged with the linux kernel packge. As a result, going forward, bugs that would have been reported against linux-ubuntu-modules should now just be reported against linux.

And finally, Bjorn, since you are the original bug reporter, can you comment if this is resolved for you with Hardy?

Thanks again everyone and we appreciate your help and feedback.

[Jonathan Thomas (echidnaman)]

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!