From: Larry Finger <Larry.Finger@lwfinger.net>
To: Francesco Gringoli <francesco.gringoli@ing.unibs.it>
Cc: Broadcom Wireless <bcm43xx-dev@lists.berlios.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
Michael Buesch <mb@bu3sch.de>
Subject: Re: [PATCH] b43: Rewrite DMA Tx status handling sanity checks
Date: Mon, 23 Nov 2009 09:41:56 -0600 [thread overview]
Message-ID: <4B0AAD44.2090908@lwfinger.net> (raw)
In-Reply-To: <5A2C6B7F-5617-49AA-B22A-A5574D6CD9FA@ing.unibs.it>
On 11/23/2009 05:00 AM, Francesco Gringoli wrote:
>
> so you can observe this behavior at your site. Do you mind describing
> the exact configuration? Maybe this time I can reproduce this behavior,
> as I tried everything to make it happen. I also asked Larry one of his
> boards and put it into several PCs but had no chance to reproduce the
> crash. Could you please also report the neighboring stations, the AP you
> are connected and so on.
As Michael said, I was the one that reported the behavior. My card was a BCM4318
in a Cardbus format running V5.2 of the openfwwf. The AP is a Linksys WRT54G V5
running standard firmware v1.02.6. A list of nearby AP's with channels and
strengths are as follows:
Cell 01 - Address: 00:14:BF:85:49:FA
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=70/70 Signal level=-6 dBm
Encryption key:on (WPA2)
ESSID:"lwfdjf_rad"
Cell 02 - Address: 00:1B:11:5C:B0:83
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=25/70 Signal level=-85 dBm
Encryption key:on (WEP)
ESSID:"Browns"
Cell 03 - Address: 00:1A:70:46:BA:B1
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=42/70 Signal level=-68 dBm
Encryption key:on (WEP)
ESSID:"Larry with space"
Cell 04 - Address: 00:23:69:81:B7:D9
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=34/70 Signal level=-76 dBm
Encryption key:on (WEP)
ESSID:"Hoover"
Cell 05 - Address: 00:14:BF:0C:7E:14
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=28/70 Signal level=-82 dBm
Encryption key:on (WPA)
ESSID:"linksys"
Cell 06 - Address: 00:22:6B:78:18:7D
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=26/70 Signal level=-84 dBm
Encryption key:on (WPA)
ESSID:"Go Away"
I was connected to the AP in Cell 01. The test was my usual with a repeating
tcpperf run in one terminal and a flood ping to the same server in a second.
Please let me know if I missed any useful information.
This condition may take a long time to show up. For instance, my latest test ran
for 25 hours before failure. All other tests have failed much more quickly, but
one never knows. I have not seen this failure with standard firmware.
Larry
Larry
prev parent reply other threads:[~2009-11-23 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 21:24 [PATCH] b43: Rewrite DMA Tx status handling sanity checks Michael Buesch
2009-11-22 17:52 ` Michael Buesch
2009-11-22 18:11 ` Larry Finger
2009-11-22 18:19 ` Michael Buesch
2009-11-23 1:34 ` Larry Finger
2009-11-23 10:30 ` Michael Buesch
2009-11-23 4:45 ` Larry Finger
2009-11-23 10:49 ` Michael Buesch
2009-11-23 11:00 ` Francesco Gringoli
2009-11-23 11:05 ` Michael Buesch
2009-11-23 15:41 ` Larry Finger [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=4B0AAD44.2090908@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=francesco.gringoli@ing.unibs.it \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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.