From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-wireless@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
ipw3945-devel@lists.sourceforge.net, yi.zhu@intel.com
Subject: Re: iwl3945 in 2.6.24-rc1 dies under load
Date: Thu, 1 Nov 2007 02:59:04 +0100 [thread overview]
Message-ID: <200711010259.05315.rjw@sisk.pl> (raw)
In-Reply-To: <20071031005202.GA1534@elf.ucw.cz>
On Wednesday, 31 October 2007 01:52, Pavel Machek wrote:
>
> Hi!
>
> ...does not seem to work too well :-(. It connects with the AP
> (good!), and survives some "normal" use, but it died at first big
> tcpspray (baaaad!).
Is this a regression from 2.6.23?
> Oct 31 01:03:57 amd log1n[1411]: ROOT LOGIN on `tty6'
> Oct 31 01:05:06 amd kernel: iwl3945: Intel(R) PRO/Wireless 3945ABG/BG
> Network Connection driver for Linux, 1.1.17kds
> Oct 31 01:05:06 amd kernel: iwl3945: Copyright(c) 2003-2007 Intel
> Corporation
> Oct 31 01:05:06 amd kernel: PCI: Setting latency timer of device
> 0000:03:00.0 to 64
> Oct 31 01:05:06 amd kernel: iwl3945: Detected Intel PRO/Wireless
> 3945ABG Network Connection
> Oct 31 01:05:07 amd kernel: iwl3945: Tunable channels: 11 802.11bg, 13
> 802.11a channels
> Oct 31 01:05:07 amd kernel: phy4: Selected rate control algorithm
> 'simple'
> Oct 31 01:06:05 amd kernel: wlan0: Initial auth_alg=0
> Oct 31 01:06:05 amd kernel: wlan0: authenticate with AP
> 00:11:2f:0e:95:a0
> Oct 31 01:06:05 amd kernel: wlan0: RX authentication from
> 00:11:2f:0e:95:a0 (alg=0 transaction=2 status=0)
> Oct 31 01:06:05 amd kernel: wlan0: authenticated
> Oct 31 01:06:05 amd kernel: wlan0: associate with AP 00:11:2f:0e:95:a0
> Oct 31 01:06:05 amd kernel: wlan0: RX AssocResp from 00:11:2f:0e:95:a0
> (capab=0x401 status=0 aid=1)
> Oct 31 01:06:05 amd kernel: wlan0: associated
> Oct 31 01:06:05 amd kernel: wlan0: switched to short barker preamble
> (BSSID=00:11:2f:0e:95:a0)
> Oct 31 01:06:05 amd kernel: iwl3945: iwl-3945-rs not selected as rate
> control algo!
> Oct 31 01:23:52 amd kernel: wlan0: RX deauthentication from
> 00:11:2f:0e:95:a0 (reason=4)
> Oct 31 01:23:52 amd kernel: wlan0: deauthenticated
> Oct 31 01:23:53 amd kernel: wlan0: authenticate with AP
> 00:11:2f:0e:95:a0
> Oct 31 01:23:53 amd kernel: wlan0: RX authentication from
> 00:11:2f:0e:95:a0 (alg=0 transaction=2 status=0)
> Oct 31 01:23:53 amd kernel: wlan0: authenticated
> Oct 31 01:23:53 amd kernel: wlan0: associate with AP 00:11:2f:0e:95:a0
> Oct 31 01:23:53 amd kernel: wlan0: RX ReassocResp from
> 00:11:2f:0e:95:a0 (capab=0x401 status=0 aid=1)
> Oct 31 01:23:53 amd kernel: wlan0: associated
> Oct 31 01:23:53 amd kernel: wlan0: switched to short barker preamble
> (BSSID=00:11:2f:0e:95:a0)
> Oct 31 01:23:53 amd kernel: iwl3945: iwl-3945-rs not selected as rate
> control algo!
> Oct 31 01:23:53 amd kernel: wlan0: CTS protection enabled
> (BSSID=00:11:2f:0e:95:a0)
> Oct 31 01:23:53 amd kernel: wlan0: switched to long barker preamble
> (BSSID=00:11:2f:0e:95:a0)
> Oct 31 01:35:44 amd -- MARK --
> Oct 31 01:38:16 amd kernel: iwl3945: Microcode SW error detected.
> Restarting 0x82000008.
> Oct 31 01:38:16 amd kernel: iwl3945: Error Reply type 0x00000005 cmd
> REPLY_TX (0x1C) seq 0x0267 ser 0x0000004B
> Oct 31 01:38:18 amd kernel: iwl3945: Can't stop Rx DMA.
>
> ...unfortunately, microcode sources are not available so Intel should
> fix this, right?
>
> (Actually, it recovered after 3 minutes):
>
> Oct 31 01:41:15 amd kernel: wlan0: RX deauthentication from
> 00:11:2f:0e:95:a0 (reason=4)
> Oct 31 01:41:15 amd kernel: wlan0: deauthenticated
> Oct 31 01:41:16 amd kernel: wlan0: authenticate with AP
> 00:11:2f:0e:95:a0
> Oct 31 01:41:16 amd kernel: wlan0: RX authentication from
> 00:11:2f:0e:95:a0 (alg=0 transaction=2 status=0)
> Oct 31 01:41:16 amd kernel: wlan0: authenticated
> Oct 31 01:41:16 amd kernel: wlan0: associate with AP 00:11:2f:0e:95:a0
> Oct 31 01:41:16 amd kernel: wlan0: RX ReassocResp from
> 00:11:2f:0e:95:a0 (capab=0x401 status=0 aid=1)
> Oct 31 01:41:16 amd kernel: wlan0: associated
> Oct 31 01:41:16 amd kernel: wlan0: CTS protection enabled
> (BSSID=00:11:2f:0e:95:a0)
> Oct 31 01:41:16 amd kernel: iwl3945: iwl-3945-rs not selected as rate
> control algo!
> Oct 31 01:41:16 amd kernel: wlan0: switched to short barker preamble
> (BSSID=00:11:2f:0e:95:a0)
>
> Hmm, and it is pretty reproducible, with:
>
> tcpspray -n 1 -b 10000000 10.0.0.2
>
> Oct 31 01:42:56 amd kernel: iwl3945: Microcode SW error detected.
> Restarting 0x82000008.
> Oct 31 01:42:56 amd kernel: iwl3945: Error Reply type 0x00000005 cmd
> REPLY_TX (0x1C) seq 0x02C7 ser 0x0000004B
> Oct 31 01:42:58 amd kernel: iwl3945: Can't stop Rx DMA.
next prev parent reply other threads:[~2007-11-01 1:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 0:52 iwl3945 in 2.6.24-rc1 dies under load Pavel Machek
2007-10-31 0:54 ` Zhu Yi
2007-10-31 11:05 ` Pavel Machek
2007-10-31 12:01 ` [ipw3945-devel] " Pablo Sanchez
2007-11-01 0:12 ` Pavel Machek
2007-11-01 1:37 ` Zhu Yi
2007-11-01 5:52 ` [ipw3945-devel] " mabbas
2007-11-03 18:34 ` Pavel Machek
2007-11-04 10:28 ` [ipw3945-devel] " drago01
2007-10-31 0:59 ` dragoran
2007-11-01 1:59 ` Rafael J. Wysocki [this message]
2007-11-01 8:22 ` Rolf Eike Beer
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=200711010259.05315.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pavel@ucw.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.