linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mirco Tischler <mt-ml@gmx.de>
To: Leonid Podolny <leonidp.lists@gmail.com>
Cc: linux-kernel@vger.kernel.org, yi.zhu@intel.com,
	reinette.chatre@intel.com, linux-wireless@vger.kernel.org,
	IvDoorn@gmail.com
Subject: Re: CPU load after killing iwlagn with RF kill switch
Date: Sun, 17 Aug 2008 03:59:21 +0200	[thread overview]
Message-ID: <20080817035921.4d35ae0e@mtlp.12thdimension> (raw)
In-Reply-To: <48A5EC02.4070303@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2072 bytes --]

On Fri, 15 Aug 2008 23:50:10 +0300, Leonid Podolny wrote:
> Hi,
> With a new iwlagn driver and 2.6.27-rc3, if I turn off the wireless 
> (intel 4965ag) by RF kill switch, the CPU utilization of ksoftirqd 
> process raises to 100% and stays there until I rmmod the module.
> Please let me know what further information I can provide.

Hi

Same on my machine with same chip and same kernel.
If I use the switch on the side of my laptop to turn off wlan, ksoftirqd eats
up one core of my cpu til I switch it on again or rmmod the iwlagn module. But
when I switch it on before the device loses connection and then off a second
time, I now get a (the) second ksoftirqd process eating up the other core too.
This only happens if a connection is established, though.
I'm not sure if this problem existed in 2.6.26 but I doubt it. (Will check if I
find the time).

My dmesg shows me this:

[48067.257539] iwlagn: Radio Frequency Kill Switch is On:
[48067.257539] Kill switch must be turned off for wireless networking to work.
[48071.295154] wlan0: No ProbeResp from current AP 00:c0:a8:e5:e5:a5 - assume
out of range 
[48072.099173] iwlagn: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 
[48072.099260] mac80211-phy1: failed to remove key (0, 00:c0:a8:e5:e5:a5) from
hardware (-5) 
[48072.206028] iwlagn: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 
[48072.206028] mac80211-phy1: failed to remove key (1, ff:ff:ff:ff:ff:ff) from
hardware (-5)

The probably interesting parts of my config look like that:

CONFIG_IWLWIFI=m
CONFIG_IWLCORE=m
CONFIG_IWLWIFI_LEDS=y
CONFIG_IWLWIFI_RFKILL=y
# CONFIG_IWLWIFI_DEBUG is not set
CONFIG_IWLAGN=m
CONFIG_IWLAGN_SPECTRUM_MEASUREMENT=y
CONFIG_IWLAGN_LEDS=y
CONFIG_IWL4965=y
# CONFIG_IWL5000 is not set
# CONFIG_IWL3945 is not set

CONFIG_RFKILL=m
# CONFIG_RFKILL_INPUT is not set
CONFIG_RFKILL_LEDS=y
CONFIG_IWLWIFI_RFKILL=y

I can recompile with debug options set if this helps. Just haven't found the
time.

Thanks
Mirco

P.S.: added some cc's for iwlwifi and rfkill.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

       reply	other threads:[~2008-08-17  1:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48A5EC02.4070303@gmail.com>
2008-08-17  1:59 ` Mirco Tischler [this message]
2008-08-17  7:04   ` CPU load after killing iwlagn with RF kill switch Tomas Winkler
2008-08-17 15:02     ` John W. Linville
2008-08-17 16:20       ` Tomas Winkler
2008-08-17 17:07         ` John W. Linville
2008-08-17 18:01           ` Tomas Winkler
2008-08-25 19:31             ` Luis R. Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080817035921.4d35ae0e@mtlp.12thdimension \
    --to=mt-ml@gmx.de \
    --cc=IvDoorn@gmail.com \
    --cc=leonidp.lists@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=yi.zhu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).