linux-kernel - Re: iwlagn: wrong command queue 31, command id 0x0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 6 Nov 2008 22:06:17 -0800
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	"Matt Mackall" <mpm@...enic.com>
Cc:	"Marcel Holtmann" <holtmann@...ux.intel.com>,
	"Zhu Yi" <yi.zhu@...el.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	linux-wireless <linux-wireless@...r.kernel.org>
Subject: Re: iwlagn: wrong command queue 31, command id 0x0

On Thu, Nov 6, 2008 at 9:58 PM, Matt Mackall <mpm@...enic.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/