All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederik Himpe <fhimpe@telenet.be>
To: linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: iwlagn: associating with AP causes kernel hiccup
Date: Fri, 17 Oct 2008 12:06:08 +0000 (UTC)	[thread overview]
Message-ID: <gd9v3f$3ft$1@ger.gmane.org> (raw)
In-Reply-To: 1224104363.19219.30.camel@rc-desk

On Wed, 15 Oct 2008 13:59:23 -0700, reinette chatre wrote:

> On Wed, 2008-10-15 at 19:38 +0000, Frederik Himpe wrote:
>> When I associate with an AP, Linux 2.6.27 seems to "hang" for a few
>> seconds. During that time, all sound stops playing and keyboard and
>> mouse input is impossible. In the log I see this:
>> 
>> wlan0: authenticate with AP 00:15:f2:0a:ab:43 wlan0: authenticate with
>> AP 00:15:f2:0a:ab:43 wlan0: authenticate with AP 00:15:f2:0a:ab:43
>> wlan0: authenticated
>> wlan0: associate with AP 00:15:f2:0a:ab:43 wlan0: RX AssocResp from
>> 00:15:f2:0a:ab:43 (capab=0x431 status=0 aid=2) wlan0: associated
>> ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready iwlagn 0000:0c:00.0:
>> PCI INT A disabled iwlagn 0000:0c:00.0: PCI INT A -> GSI 17 (level,
>> low) -> IRQ 17 iwlagn 0000:0c:00.0: restoring config space at offset
>> 0x1 (was 0x100102, writing 0x100106)
> 
> Are you running wpa_supplicant and/or network manager?

I'm using Mandriva 2009.0 x86_64 with wpa_supplicant and Mandriva's 
wireless network configuration tool (drakroam).

> Can you try testing without them?

Actually I just found out that running
# ifconfig wlan0 down
is enough to trigger the sound and mouse hanging for a few seconds.

This is what appears in the kernel logs when running that command:

Oct 17 14:04:51 defected kernel: iwlagn 0000:0c:00.0: PCI INT A disabled
Oct 17 14:04:52 defected kernel: iwlagn 0000:0c:00.0: PCI INT A -> GSI 17 
(level, low) -> IRQ 17
Oct 17 14:04:52 defected kernel: iwlagn 0000:0c:00.0: restoring config 
space at offset 0x1 (was 0x100102, writing 0x100106)
Oct 17 14:04:52 defected kernel: Registered led device: iwl-phy0:radio
Oct 17 14:04:52 defected kernel: Registered led device: iwl-phy0:assoc
Oct 17 14:04:52 defected kernel: Registered led device: iwl-phy0:RX
Oct 17 14:04:52 defected kernel: Registered led device: iwl-phy0:TX
Oct 17 14:04:52 defected kernel: ADDRCONF(NETDEV_UP): wlan0: link is not 
ready

-- 
Frederik Himpe



  reply	other threads:[~2008-10-17 12:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 19:38 iwlagn: associating with AP causes kernel hiccup Frederik Himpe
2008-10-15 20:59 ` reinette chatre
2008-10-17 12:06   ` Frederik Himpe [this message]
2008-10-17 12:18     ` Frederik Himpe
2008-10-17 15:27       ` Richard Scherping
2008-10-17 20:02         ` Tomas Winkler
2008-10-18 16:17           ` Richard Scherping
2008-10-19 15:18             ` Andy Lutomirski
2008-10-19 22:12               ` Tomas Winkler
2008-10-19 22:52                 ` Andrew Lutomirski
2008-10-19 23:12                   ` Tomas Winkler

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='gd9v3f$3ft$1@ger.gmane.org' \
    --to=fhimpe@telenet.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.