linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Olivier Crête" <olivier.crete@ocrete.ca>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Sometimes rtl8187 stops sending/receiving packets under load
Date: Sat, 16 Jul 2011 21:06:25 -0400	[thread overview]
Message-ID: <1310864785.3540.5.camel@TesterBox.tester.ca> (raw)
In-Reply-To: <4E221A18.2070504@lwfinger.net>

[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]

On Sat, 2011-07-16 at 18:09 -0500, Larry Finger wrote:
> On 07/16/2011 04:17 PM, Olivier Crête wrote:
> > I get this on my dmesg:
> > ieee80211 phy0: wlan0: No probe response from AP 00:0f:66:e2:5f:dd after 500ms, disconnecting.
> > cfg80211: Calling CRDA to update world regulatory domain
> > wlan0: authenticate with 00:0f:66:e2:5f:dd (try 1)
> > wlan0: authenticate with 00:0f:66:e2:5f:dd (try 2)
> > wlan0: authenticate with 00:0f:66:e2:5f:dd (try 3)
> > wlan0: authentication with 00:0f:66:e2:5f:dd timed out
> >
> > The wireless card is the one built-in a Asus P5K-E/wifi-ap motherboard.
> > And the router is a WRT54G v2 running the latest OpenWRT.
> >
> > This bit of dmesg output may also be useful:
> > usb 1-3: reset high speed USB device using ehci_hcd and address 2
> > cfg80211: Calling CRDA to update world regulatory domain
> > ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
> > ieee80211 phy0: hwaddr 00:15:af:37:19:b3, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 2
> 
> I have the same device as you as shown in the following:
> 
> ieee80211 phy1: hwaddr 00:1b:2f:a2:07:ca, RTL8187vB (default) V1 + rtl8225z2, 
> rfkill mask 2
> 
> I have run this card extensively in the past several months and have not seen 
> any problems. One of my APs is a WRT54GL running a fairly recent openWRT.
> 
> Does this only happen when running torrents, or does it happen with a different 
> heavy load?

I can only reproduce it with torrents, downloading something with a
single TCP connection doesn't crash. So my guess it has something to do
with the upload side maybe or maybe with loading both directions at the
same time.

> Please try to repeat with a 2.6.39 or 3.0 kernel.

Alright, upgraded to 3.0-rc7 and I could still reproduce it in less than
10 minutes. 

-- 
Olivier Crête
olivier.crete@ocrete.ca

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-07-17  5:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16 21:17 Sometimes rtl8187 stops sending/receiving packets under load Olivier Crête
2011-07-16 23:09 ` Larry Finger
2011-07-17  1:06   ` Olivier Crête [this message]
2011-07-17  6:02     ` Andreas Hartmann
     [not found]     ` <4E228ADC.70606@01019freenet.de>
     [not found]       ` <1313809445.12189.2.camel@TesterBox.tester.ca>
     [not found]         ` <4E4F27A1.3050608@lwfinger.net>
2011-10-02  8:32           ` Olivier Crête
2011-10-02 16:34             ` Larry Finger

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=1310864785.3540.5.camel@TesterBox.tester.ca \
    --to=olivier.crete@ocrete.ca \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).