From: Richard Scherping <richard@scherping.de>
To: Frederik Himpe <fhimpe@telenet.be>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: iwlagn: associating with AP causes kernel hiccup
Date: Fri, 17 Oct 2008 17:27:45 +0200 [thread overview]
Message-ID: <48F8AEF1.5030603@scherping.de> (raw)
In-Reply-To: <gd9vpo$5ql$1@ger.gmane.org>
>>>> 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.
>>
>> I'm using Mandriva 2009.0 x86_64 with wpa_supplicant and Mandriva's
>> wireless network configuration tool (drakroam).
>>
>> Actually I just found out that running # ifconfig wlan0 down
>> is enough to trigger the sound and mouse hanging for a few seconds.
>
> And shortly after I wrote that, while associating while getting an IP
> with dhclient when associating with a WPA encrypted AP, I got this
> backtrace in my logs:
> [...]
I have a similar problem here. No crash up to now, but the very same "hang" for a few seconds on "ifconfig wlan0 down". Interestingly this does only happen after a normal boot - once I did a suspend and resume (S3), there is no hang anymore.
Hardware: Thinkpad T61p with Intel 4965 agn
Software: Debian Lenny x86_64 with vanilla 2.6.27 kernel
I remember having the same "hang" with older kernels, too.
Richard
next prev parent reply other threads:[~2008-10-17 15:27 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
2008-10-17 12:18 ` Frederik Himpe
2008-10-17 15:27 ` Richard Scherping [this message]
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=48F8AEF1.5030603@scherping.de \
--to=richard@scherping.de \
--cc=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 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).