linux-kernel - Re: 3.1+ iwlwifi lockup

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CANUX_P3bFpKyePkgYwQUO0Y3XN=B+7YHSsD81Vt=LwK6ZbrD6g@mail.gmail.com>
Date:	Fri, 25 Nov 2011 14:11:22 +0200
From:	Emmanuel Grumbach <egrumbach@...il.com>
To:	Dave Jones <davej@...hat.com>,
	"Guy, Wey-Yi" <wey-yi.w.guy@...el.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: 3.1+ iwlwifi lockup

Hi

I looked again at your stack strace, we need more debug. Please enable
Rx debug flag: 0x1000000.

What is happening here is that the HW (the Flow Handler for instance),
is closing an empty RB (Receive Buffer). The beginning of the buffer
is 0x00005555 which is the maker of "End of Buffer" of the Flow
Handler. The marker helps the driver to understand that there is no
more useful data in the buffer.
So basically what we are seeing here is that the FH is sending an
empty buffer. Which is not nice.
This can very well be a bug in the read / write pointers in the Rx
flow, or something in that region.

On Wed, Nov 23, 2011 at 06:17, Dave Jones <davej@...hat.com> wrote:
> On Tue, Nov 22, 2011 at 06:56:05PM -0800, Guy, Wey-Yi wrote:
>  > Agree, that is why I could not re-produce here after many try. Could you
>  > share your configuration, such as
>
>  > band/channel
>
> Channel:1
> Frequency:2.412 GHz (Channel 1)
>
>  > 32/64 bit system
>
> 64bit. It's a Dell Adamo laptop.
>
>  > 20/40 MHz
>
> not sure how to find out what you're looking for.
>
>  > traffic type
>
> last triggered it with just ssh.
>
>  > open/security
>
> IE: IEEE 802.11i/WPA2 Version 1
>    Group Cipher : CCMP
>    Pairwise Ciphers (1) : CCMP
>    Authentication Suites (1) : PSK
>
>  > power management
>
> nothing special. everything is default.
>
> all messages related to iwlwifi in dmesg are below..
>
>        Dave
>
> [   24.423300] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d
> [   24.425560] Copyright(c) 2003-2011 Intel Corporation
> [   24.428667] iwlwifi 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> [   24.437959] iwlwifi 0000:04:00.0: setting latency timer to 64
> [   24.438108] iwlwifi 0000:04:00.0: pci_resource_len = 0x00002000
> [   24.444058] iwlwifi 0000:04:00.0: pci_resource_base = ffffc90011574000
> [   24.445823] iwlwifi 0000:04:00.0: HW Revision ID = 0x0
> [   24.447695] iwlwifi 0000:04:00.0: irq 46 for MSI/MSI-X
> [   24.447896] iwlwifi 0000:04:00.0: Detected Intel(R) Ultimate N WiFi Link 5300 AGN, REV=0x24
> [   24.453070] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
> [   24.486217] iwlwifi 0000:04:00.0: device EEPROM VER=0x120, CALIB=0x4
> [   24.489176] iwlwifi 0000:04:00.0: Device SKU: 0Xf0
> [   24.490778] iwlwifi 0000:04:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
> [   24.520548] iwlwifi 0000:04:00.0: loaded firmware version 8.83.5.1 build 33692
> [   39.229498] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
> [   39.240818] iwlwifi 0000:04:00.0: Radio type=0x0-0x2-0x0
> [   39.607327] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
> [   39.613424] iwlwifi 0000:04:00.0: Radio type=0x0-0x2-0x0
> [  210.248807] iwlwifi 0000:04:00.0: Tx aggregation enabled on ra = b8:c7:5d:0c:39:87 tid = 6
--
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/