linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Iordan Iordanov <iiordanov@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Fwd: Atheros AR5418 with Ath9k driver hangs during file transfer
Date: Wed, 03 Feb 2010 12:14:53 -0500	[thread overview]
Message-ID: <1265217293.22737.11.camel@mj> (raw)
In-Reply-To: <43075fc61002030846k3218de12o6f0f77fd691499cb@mail.gmail.com>

On Wed, 2010-02-03 at 11:46 -0500, Iordan Iordanov wrote:

> When I start a file transfer over wireless (from an NFS mount), I
> achieve about 8.5MB/s for a while, and then the transfer hangs. Also,
> any other network communication is hung as well it seems indefinitely.

The log seems to show that you are very short on memory.  The backtraces
come from "page allocation failure", not from any conditions in the
ath9k driver.  You have a lot of free swap, so I assume it's the
non-swappable memory.  This is also evidenced by lowmem_reserve:

lowmem_reserve[]: 0 0 0 0

I haven't heard of any major memory leaks in ath9k, so I would not blame
it on the driver unless you can show that you don't get that problem
with another driver.

In the future, please send kernel logs produced by the dmesg command.
This will avoid the timestamps from syslogd (especially since you
already have kernel timestamps) and it would ensure that no kernel
messages are skipped by syslogd because of their low urgency.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2010-02-03 17:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28  6:07 Atheros AR5418 with Ath9k driver hangs during file transfer Iordan Iordanov
2010-02-03 16:46 ` Fwd: " Iordan Iordanov
2010-02-03 17:14   ` Pavel Roskin [this message]
2010-02-03 17:24     ` Iordan Iordanov
2010-02-03 21:48       ` Pavel Roskin

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=1265217293.22737.11.camel@mj \
    --to=proski@gnu.org \
    --cc=iiordanov@gmail.com \
    --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).