Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Weird Atheros 9485 http connecting problems
Date: Tue, 27 May 2014 17:13:27 +0530	[thread overview]
Message-ID: <20140527114325.GA11035@qca.qualcomm.com> (raw)
In-Reply-To: <538382C1.40804@gmail.com>

On Mon, May 26, 2014 at 03:06:57PM -0300, Oskar Kossuth wrote:
> Update:
> 
> I did some investigation after the problem with the atheros wifi card
> happened again and i found something odd.
> The firefox process was consuming a lot of CPU, while the problem was
> ongoing, and the CPU usage decreased to normal levels after i stopped trying
> to load a website, and increased a lot after i tried to load the website
> again.
>
Oskar,

your issue is not related to firefox as earlier you had mentioned that
with lynx also the problem occurs. isn't it?
> 
> PS: I tested using the eth0 realtek adapter of my laptop and disabled
> wireless. The problem appeared also in this case.
> 
So it is not wireless or ethernet issue. From you earlier sniffer
capture, I do see lot of TCP connection resets with window size 0.
Even TCP 3-way handshake also terminated in most of the cases. Can you
tune TCP receive buffer size.

http://www.cyberciti.biz/faq/linux-tcp-tuning/

-Rajkumar

  reply	other threads:[~2014-05-27 11:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 13:46 [ath9k-devel] Weird Atheros 9485 http connecting problems Arkh4mKn1ght
2014-05-15 12:37 ` Rajkumar Manoharan
2014-05-15 12:57   ` Arkh4mKn1ght
2014-05-15 16:06     ` Rajkumar Manoharan
2014-05-15 17:44       ` Arkh4mKn1ght
2014-05-15 23:02       ` Arkh4mKn1ght
2014-05-16  9:06         ` Rajkumar Manoharan
2014-05-16 12:22           ` Arkh4mKn1ght
2014-05-18 23:51             ` Adrian Chadd
2014-05-19  0:29               ` Arkh4mKn1ght
2014-05-19  6:10                 ` Adrian Chadd
2014-05-19 13:12                   ` Arkh4mKn1ght
2014-05-19  6:29                 ` Rajkumar Manoharan
2014-05-19 13:12                   ` Arkh4mKn1ght
2014-05-19 14:42                     ` Rajkumar Manoharan
2014-05-20  0:32                       ` Adrian Chadd
2014-05-20 14:34                         ` Arkh4mKn1ght
2014-05-21 14:37                         ` Arkh4mKn1ght
2014-05-21 14:59                           ` Rajkumar Manoharan
2014-05-21 15:10                             ` Arkh4mKn1ght
2014-05-21 19:04                               ` Kyle Bassett
2014-05-21 20:51                                 ` Arkh4mKn1ght
2014-05-21 20:10                               ` Adrian Chadd
2014-05-21 20:52                                 ` Arkh4mKn1ght
2014-05-21 22:05                                   ` Adrian Chadd
2014-05-23  0:50                                 ` Arkh4mKn1ght
2014-05-26 18:06                                 ` Oskar Kossuth
2014-05-27 11:43                                   ` Rajkumar Manoharan [this message]
2014-05-27 13:52                                     ` Arkh4mKn1ght
2014-05-21 15:39                             ` [ath9k-devel] Weird Atheros 9485 http connecting problems - Sniffer Capture Arkh4mKn1ght

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=20140527114325.GA11035@qca.qualcomm.com \
    --to=rmanohar@qti.qualcomm.com \
    --cc=ath9k-devel@lists.ath9k.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