Failure to suspend, shutdown, or hibernate using iwl3945.

Bug #130457 reported by Jeremy Teale on 2007-08-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-ubuntu-modules-2.6.22 (Ubuntu)
Nominated for Gutsy by Mackenzie Morgan

Bug Description

When attempting to suspend, shutdown, or hibernate, syslog repeatedly reports:
hermes kernel: [12398.272000] unregister_netdevice: waiting for wlan0_rename to become free. Usage count = 1

I am forced to power off the computer manually as it becomes unresponsive.

I'm not sure if this is a NetworkManager problem, or an issue with the driver.

My network card as reported by lspci:
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

Jeremy Teale (jteale) on 2007-08-05
description: updated
Jeremy Teale (jteale) on 2007-08-05
Changed in linux-ubuntu-modules-2.6.22:
importance: Undecided → High
Chris Halse Rogers (raof) wrote :

I also see this, although the usage count is not always 1, it is sometimes higher.
Upstream bug:

03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

Matteo Collina (matteo-collina) wrote :

I'm confirming this too but only on suspend and hibernate.

02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02).

Putting "networking" in /etc/default/acpi-support STOP_SERVICES made suspend and hibernate works but on resume NM doesn't configure the network.

Matteo Collina (matteo-collina) wrote :

I've done a little workaround to make suspend/hibernate work with the iwl3945 driver.
First of all I've put in /etc/default/acpi-support MODULES_WHITELIST="iwl3945"
Secondly I've added this script under /etc/acpi/resume.d

/etc/dbus-1/event.d/25NetworkManager restart
/etc/dbus-1/event.d/26NetworkManagerDispatcher restart

In this way NetworkManager is restarted and it reconfigure the wifi card.

It's not a good practice but it solved the problem for me.

nanog (sorenimpey) wrote :

I have this same bug. Occasional SysRq hard locks or suspend failures. 3945ABG specific as it does not occur with a different wireless card in same laptop.

 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

HAL quirck checker output
-e Checking your system...

WARNING: You have no quirks!
WARNING: Using broadcom network driver.
CRITICAL ERROR: Use the mac80211 based iwl3945 driver instead. ipw3945d is closed source sometimes hangs on resume.

Let me know if there is any additional info needed.

curiocheerio (aaronszymanski) wrote :

I have the same issue as well, but with an rt73 chip set. After resuming from a suspend wireless no longer works. Then when i shut down my system it hangs with the unregister_device error repeating. The only way to restart at this point is to cut the power.

Tim Gardner (timg-tpi) wrote :

Update according to instructions in You'll also have to blacklist the ipw3945 driver in /etc/modprobe.d/blacklist

Changed in linux-ubuntu-modules-2.6.22:
assignee: nobody → timg-tpi
importance: High → Medium
milestone: none → gutsy-updates
status: New → Fix Committed
Tim Gardner (timg-tpi) wrote :

Try using iwl3945 in Hardy. The suspend/hibernate architecture in 2.6.24 is much improved.

Changed in linux-ubuntu-modules-2.6.22:
assignee: timg-tpi → nobody
status: Fix Committed → Won't Fix
Andres Mujica (andres.mujica) wrote :

for the suspend issue could you check the workaround from this bug report?


Andres Mujica (andres.mujica) wrote :

Solving the wlan0_rename issue i could suspend again with network support upon wake up and adding iwl3945 to MODULES in /etc/default/acpi-support let me hibernate again. The only issue is that connecting again to the wireless lan take a few seconds (almost a minute).

However reading what acpi-support comments indicate the network unloading module should be automatically done, so maybe in gutsy the iwl3945 is not configured in acpi for this to happen.

# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST

Anyway as iwl3945 is not the default Intel 3945 driver for Gutsy this probably would get fixed for hardy only if the problem arises there.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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