From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Theodore Tso <tytso@mit.edu>,
yi.zhu@intel.com, reinette.chatre@intel.com,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Potential iwlwifi locking problem in 2.6.26-git9
Date: Wed, 23 Jul 2008 15:24:54 -0700 [thread overview]
Message-ID: <4887AFB6.2060802@goop.org> (raw)
In-Reply-To: <20080723214938.GA8034@mit.edu>
Theodore Tso wrote:
> On Wed, Jul 23, 2008 at 05:36:30PM -0400, Theodore Ts'o wrote:
>
>> Is this a new one? I don't think I've seen this on LKML....
>>
>
> The context of this was I had just booted to 2.6.26-git9, noted with
> annoyance that that the iwl4965 driver needed a new microcode file, so
> I popped in my EVDO card, downloaded the firmware, moved the firmware
> into place, and then got the above error message.
>
> I've since noted that it seems to be utterly refusing to associate
> with my wireless access point. This was working just fine with
> 2.6.26-git6 kernel, so it looks like a recent regression? I just
> noticed someone else had recently complained about a similar "refusal
> to associate" with the iwl3945 driver.
>
I noticed the same thing last night; a current git build goes through
all the motions, but then fails to associate.
J
next prev parent reply other threads:[~2008-07-23 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 21:36 Potential iwlwifi locking problem in 2.6.26-git9 Theodore Ts'o
2008-07-23 21:49 ` Theodore Tso
2008-07-23 22:02 ` Tomas Winkler
2008-07-23 22:59 ` Carlos R. Mafra
2008-07-23 23:11 ` David Miller
2008-07-23 23:35 ` Carlos R. Mafra
2008-07-23 22:24 ` Jeremy Fitzhardinge [this message]
2008-07-23 22:20 ` David Miller
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=4887AFB6.2060802@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=tytso@mit.edu \
--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).