From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Matt Mackall" <mpm@selenic.com>
Cc: "Marcel Holtmann" <holtmann@linux.intel.com>,
"Zhu Yi" <yi.zhu@intel.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: wrong command queue 31, command id 0x0
Date: Thu, 6 Nov 2008 22:06:17 -0800 [thread overview]
Message-ID: <43e72e890811062206w1c2e669fnc16dc5fcf9e2d505@mail.gmail.com> (raw)
In-Reply-To: <1226037518.3023.60.camel@calx>
On Thu, Nov 6, 2008 at 9:58 PM, Matt Mackall <mpm@selenic.com> wrote:
> On Fri, 2008-11-07 at 05:40 +0100, Marcel Holtmann wrote:
>> Hi Matt,
>>
>> > [ 5470.869820] WARNING: at drivers/net/wireless/iwlwifi/iwl-tx.c:1204
>> > iwl_rx_handle+0x11a/0x21b [iwlagn]()
>> > [ 5470.869824] wrong command queue 31, command id 0x0
>>
>> I am seeing this a lot with my X61 running a 64-bit kernel/OS and my D-
>> Link DIR-615 access point. With some other access points I am seeing
>> it never or a lot less.
>
>> What kind of laptop and access point are you using? Is you access
>> point 802.11n capable? Do you run the i386 or x86_64 version of your
>> distro?
>
> Laptop is a Fujitsu 8010p. I've tried this with kernel only once with a
> G-capable Airport (with various other unknown access points in range),
> but it failed to find any networks. 64-bit kernel and Debian unstable.
>
> 2.6.27 mostly works fine here, though occasionally I need to load/unload
> iwlagn after s2ram.
FWIW I get this on 32 bit kernel, wireless-testing, 11G AP, and it
happens a lot. But its a very noisy environment.
Luis
prev parent reply other threads:[~2008-11-07 6:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 4:16 Matt Mackall
2008-11-06 17:07 ` reinette chatre
2008-11-07 1:13 ` Zhu Yi
2008-11-07 1:23 ` Matt Mackall
2008-11-07 4:37 ` Marcel Holtmann
2008-11-07 4:40 ` Marcel Holtmann
2008-11-07 5:58 ` Matt Mackall
2008-11-07 6:06 ` Luis R. Rodriguez [this message]
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=43e72e890811062206w1c2e669fnc16dc5fcf9e2d505@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=holtmann@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mpm@selenic.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
all inboxes | Powered by JetHome®