DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=E1FaTweDuH0XM+Li323wXZCjfgXsODXitYsD75NwBhWFM1p75/Fpgfqic9mMsgdIWe
         vPvkF1vOkOvGLwuXzsXEtR9c7mma57O7mTi7VFt4gjAWjueWkFOjIxaYA2BjsL2c7/DD
         JftRu2pVH0ZOi4OATQIhbf9XCDNzh0y+v24cM=
Message-ID: <43e72e890811062206w1c2e669fnc16dc5fcf9e2d505@mail.gmail.com>
Date: Thu, 6 Nov 2008 22:06:17 -0800
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Matt Mackall" <mpm@selenic.com>
Subject: Re: iwlagn: wrong command queue 31, command id 0x0
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>
In-Reply-To: <1226037518.3023.60.camel@calx>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1225944979.3792.3.camel@calx>
	 <5109BB99-53F1-499A-9D0B-FAB77591FBD5@linux.intel.com>
	 <1226037518.3023.60.camel@calx>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1343
Lines: 32

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/