ipw3945 radio kill switch on when returning from suspend

Bug #99732 reported by Jyrki Pulliainen
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.20 (Ubuntu)
Invalid
Medium
Unassigned
linux-source-2.6.20 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-restricted-modules-2.6.20-13-generic

After suspend ipw3945 wifi device doesn't wake up. Trying modprobe ipw3945 reports in dmesg the kill switch is on. Using hardware switch doesn't wake it up, only boot seems to help. Suspend was working fine with previous restricted modules

Revision history for this message
Jyrki Pulliainen (jyrki-pulliainen) wrote :
Revision history for this message
Jyrki Pulliainen (jyrki-pulliainen) wrote :
Revision history for this message
Infecto (infecto) wrote :

i`v got the same problem on ASUS F2J

Revision history for this message
Infecto (infecto) wrote :
Revision history for this message
Infecto (infecto) wrote :
Revision history for this message
Jyrki Pulliainen (jyrki-pulliainen) wrote :

As this problem persists on two users. I'm marking this confirmed.

The problem appeared on 2.6.10-13, it was working fine before (2.6.20-12 and prior)

Changed in linux-restricted-modules-2.6.20:
status: Unconfirmed → Confirmed
Revision history for this message
Ian Redfern (ian-redfern) wrote :

I'm using ipw3945 on a ThinkPad X60 with 2.6.20-13 and I don't see this - it reconnects to WiFi automatically on waking from suspend.

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

Sleeping:
Apr 3 15:22:41 betty kernel: [ 0.000000] Linux version 2.6.20-13-generic (root@palmer) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sun Mar 25 00:21:25 UTC 2007 (Ubuntu 2.6.20-13.21-generic)
Apr 3 21:00:12 betty kernel: [20273.400000] ACPI: PCI interrupt for device 0000:03:00.0 disabled
Apr 3 21:00:14 betty kernel: [20275.988000] PM: Preparing system for mem sleep
Apr 3 22:15:32 betty kernel: [20277.964000] pci 0000:03:00.0: suspend
Apr 3 22:15:32 betty kernel: [20278.120000] pci 0000:03:00.0: LATE suspend
Apr 3 22:15:32 betty kernel: [24792.120000] pci 0000:03:00.0: EARLY resume
Apr 3 22:15:32 betty kernel: [24793.264000] pci 0000:03:00.0: resuming
Apr 3 22:15:32 betty kernel: [24793.264000] PM: Writing back config space on device 0000:03:00.0 at offset 1 (was 100106, writing 100102)
Apr 3 22:15:42 betty kernel: [24803.580000] ieee80211: 802.11 data/management/control stack, git-1.1.13
Apr 3 22:15:42 betty kernel: [24803.580000] ieee80211: Copyright (C) 2004-2005 Intel Corporation <email address hidden>
Apr 3 22:15:42 betty kernel: [24803.584000] ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0mp
Apr 3 22:15:42 betty kernel: [24803.584000] ipw3945: Copyright(c) 2003-2006 Intel Corporation
Apr 3 22:15:42 betty kernel: [24803.584000] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 21
Apr 3 22:15:42 betty kernel: [24803.584000] PCI: Setting latency timer of device 0000:03:00.0 to 64
Apr 3 22:15:42 betty kernel: [24803.588000] ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Apr 3 22:15:44 betty kernel: [24805.396000] ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)

Revision history for this message
Jason Fischer (jasonfischer) wrote :

I have a related problem on a Toshiba Satellite A130. The ipw3945 card now causes the laptop to pause for a minute or two during the boot up. Everything comes up fine eventually, but it booted much faster before the last round of updates.

Revision history for this message
Jyrki Pulliainen (jyrki-pulliainen) wrote :

The problem is that I could test this with newer bios if it wouldn't crash my laptop otherwise. If I could find out a way to revert my bios to 212 I would gladly test this with 303.

Revision history for this message
Jyrki Pulliainen (jyrki-pulliainen) wrote :

Bit more debugging:

Seems that the wifi wake up or shutdown scripts are somehow broken. I don't know has there been new additions to those in 2.6.20-13.

Pressing the hotkey shuts the wlan, but it doesn't wake up after being pressed again. Modprobing it again prints "Kill Switch is on" -message to dmesg

Revision history for this message
Jyrki Pulliainen (jyrki-pulliainen) wrote :

On suspend this can be overridden by adding module to MODULES_WHITELIST in /etc/default/acpi-support

e.g.
MODULES_WHITELIST="ipw3945"

Revision history for this message
Jyrki Pulliainen (jyrki-pulliainen) wrote :

MODULES_WHITELIST seems not to help with 2.6.20-14. It works with 2.6.20-13.

More to debugging:

rf_kill for the card is: 2
(turns to 3 if echo -n 1 > .../rf_kill is ran)

power/state is 0

Revision history for this message
Infecto (infecto) wrote :

for me to MODULES_WHITELIST don`t help with solwing this problem.

Revision history for this message
Infecto (infecto) wrote :

Linux infecto-lapi 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

I've had this problem for about a month (I think since the -13 kernel came out) on my Asus V6J. At first pressing the wireless button would reenable wireless after resume (before it came back on automatically). Now I can't get wireless back on at all without a reboot.

Revision history for this message
Alexandros (akarypid) wrote :

I have the exact same problem on my ASUS W7J.

Running: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

Revision history for this message
Jyrki Pulliainen (jyrki-pulliainen) wrote : Re: [Bug 99732] Re: ipw3945 radio kill switch on when returning from suspend

Seems that it wakes up on the first suspend, but after second it
doesn't so there (propably) happens something on first resume that
makes second resume impossible. If someone could point out some ways
to debug this I'd be glad to do it.

Revision history for this message
Giuliano Procida (giuliano-procida) wrote :

I have a Dell Inspiron 6400n with pre-installed Ubuntu 7.04 (plus updates), kernel 2.6.20-16-generic #2 SMP.

Occasionally when coming out of memory suspend, certain Fn+X key combinations stop working. This includes Fn+F2 (radio kill) and Fn+F10 (optical drive eject), but not volume or brightness controls. (I also sometimes lose the whole keyboard and touchpad, but I can get those back by forcing another suspend and resume.)

The key codes are being received at some level since dmesg reports atkbd.c: Unknown key pressed... which it always does when the combination is pressed. Missing is the message from ipw3945 about the new Radio Kill switch status. Nothing I have tried fixes this, except a reboot.

Until now, I suspected the BIOS was at fault as I assumed the atkbd message meant the kernel was not processing the key event at all.

Next time I will check to see if /sys/bus/pci/drivers/ipw3945/*/rf_kill changes when the combination is pressed. In normal use it goes from 0 kill-off to 2 kill-on back to 0 again (with EBUSY for a bit just after a transition from 2 to 0).

Giuliano.

Revision history for this message
Giuliano Procida (giuliano-procida) wrote :

And a kernel log.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi J. Pulliainen,

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.

Changed in linux-restricted-modules-2.6.20:
importance: Undecided → Medium
status: Confirmed → Incomplete
Changed in linux-source-2.6.20:
status: New → Invalid
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Last time I tried to suspend on Gutsy, wireless still didn't come back. I'll test again and post the requested info.

Asus V6J with ipw3945

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Still happens on Gutsy, attaching requested information.

The kill switch is on and the button and fn+f2 don't work to turn the wireless back on.

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :
Revision history for this message
bart.snapp (bart-snapp) wrote :

I'm running gutsy on a dell D630 - Have the same problem.

Revision history for this message
Pierre R (pradermecker) wrote :

I can confirm the problem. I have an asus F7F, same kernel (2.6.22-14-generic). Wireless card is:
Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

I have the following dmesg:
ipw3945: Radio disable by HW RF kill switch option

Other log errors are :
: [ 16.088000] unsupported model F7F, trying default values
: [ 16.088000] send /proc/acpi/dsdt to the developers
: [ 16.360000] ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index (0FFFFFFFB) is beyond end of object [20070126]
: [ 16.360000] ACPI Error (psparse-0551): Method parse/execution failed [\_PR_.CPU1._PSS] (Node df84fa08), AE_AML_PACKAGE_LIMIT
: [ 16.360000] ACPI Exception (processor_perflib-0234): AE_AML_PACKAGE_LIMIT, Evaluating _PSS [20070126]
: [ 16.360000] ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index (0FFFFFFFB) is beyond end of object [20070126]
: [ 16.360000] ACPI Error (psparse-0551): Method parse/execution failed [\_PR_.CPU2._PSS] (Node df84fc18), AE_AML_PACKAGE_LIMIT
: [ 16.360000] ACPI Exception (processor_perflib-0234): AE_AML_PACKAGE_LIMIT, Evaluating _PSS [20070126]
: [ 17.328000] ppdev: user-space parallel port driver
: [ 17.548000] audit(1204915568.344:3): type=1503 operation="inode_permission" requested_mask="a" denied_mask="a" name="/dev/tty" pid=4904 profile="/usr/sbin/cupsd"
: [ 17.584000] apm: BIOS not found.
: [ 17.720000] r8169: eth0: link down
: [ 17.956000] Failure registering capabilities with primary security module.

or
dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason

I have been following the instructions found at https://help.ubuntu.com/community/WifiDocs/NetworkManager section "Suspend support" without success.

I have try STOP_SERVICES="networking" in acpi-support without success either.

Thanks for your help.

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in linux-restricted-modules-2.6.20:
status: Incomplete → Invalid
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.