linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Brian <bnc@astronomicalresearchaustralia.org>
Cc: "ath9k-devel@venema.h4ckr.net" <ath9k-devel@venema.h4ckr.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] [stable] [PATCH 1/3] ath9k: Handle -ENOMEM on RX gracefully
Date: Wed, 3 Dec 2008 18:32:28 -0800	[thread overview]
Message-ID: <20081204023228.GT6522@tesla> (raw)
In-Reply-To: <49370F49.2090602@astronomicalresearchaustralia.org>

On Wed, Dec 03, 2008 at 02:59:21PM -0800, Brian wrote:
> Luis,
> I tried to respond to your comment in bug 12110 but do not have a id yet.
> 
> Does this patch fix this bug?
> 
> 
> Here is my response
> 
> 
> I have the same problem but with wireless testing on a 2.6.28-rc6-wl kernel.
> I can run for hours if I do not use the wireless heavily.
> But will crash within 10mins if I use NX.
> (I have the NX parm turned on in the kernel)
> I also get the same symptoms re a ping that will just stop/start,
> directly before a crash. Also it starts to use my swap file. I NEVER use
> swap normally.
> Would you like me to apply the same patch and see if I can get some message?
> 
> 
> Can I get a patch for 2.6.28-rc6-wl ?

wireless-testing is now on 2.6.28-rc7, please do a git pull and
recompile and test that. It has some critical fixes for ath9k.

  Luis

  reply	other threads:[~2008-12-04  2:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 20:51 [PATCH 0/3] ath9k: several fixes ported to 2.6.27 Luis R. Rodriguez
2008-12-02 20:51 ` [PATCH] ath9k: Fix SW-IOMMU bounce buffer starvation Luis R. Rodriguez
2008-12-02 20:51   ` [PATCH] ath9k: correct expected max RX buffer size Luis R. Rodriguez
2008-12-02 20:51     ` [PATCH 1/3] ath9k: Handle -ENOMEM on RX gracefully Luis R. Rodriguez
2008-12-03  0:12       ` [stable] " Greg KH
2008-12-03  0:20         ` Luis R. Rodriguez
2008-12-03  0:24           ` John W. Linville
2008-12-03 20:19             ` [ath9k-devel] " Luis R. Rodriguez
2008-12-03 20:32               ` Greg KH
2008-12-03 21:22             ` John W. Linville
2008-12-03 22:14               ` [ath9k-devel] " Luis R. Rodriguez
2008-12-03 22:59                 ` Brian
2008-12-04  2:32                   ` Luis R. Rodriguez [this message]
2008-12-04  7:59                     ` 2.6.28-rc7-wl Brian
2008-12-04 19:19                       ` 2.6.28-rc7-wl Luis R. Rodriguez
     [not found]                         ` <49385507.3090705@astronomicalresearchaustralia.org>
     [not found]                           ` <20081204224300.GN5970@tesla>
     [not found]                             ` <493869E1.60207@astronomicalresearchaustralia.org>
2008-12-05  2:28                               ` 2.6.28-rc7-wl Luis R. Rodriguez
2008-12-02 20:57 ` [ath9k-devel] [PATCH 0/3] ath9k: several fixes ported to 2.6.27 Luis R. Rodriguez
2008-12-02 21:27 ` [stable] " Greg KH
2008-12-02 22:13   ` Luis R. Rodriguez

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=20081204023228.GT6522@tesla \
    --to=lrodriguez@atheros.com \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=bnc@astronomicalresearchaustralia.org \
    --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).