All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Problems with ath9k on IXP400, using Linux 2.6.35.8 and compat-wireless-2010-12-07
Date: Fri, 10 Dec 2010 08:07:02 -0800	[thread overview]
Message-ID: <20101210160702.GC2102@tux> (raw)
In-Reply-To: <AANLkTikdVP9CXRjjxqKwEtWeOddsFnWUv1HZRSM8B+wp@mail.gmail.com>

On Thu, Dec 09, 2010 at 11:48:15PM -0800, Mohammed Shafi wrote:
> On Fri, Dec 10, 2010 at 2:14 AM, B. James Phillippe <bryanp35@comcast.net>
> wrote:
> > Hi All,
> >
> > I'm new to this list and a bit new to using this project; hopefully I'm not
> > doing something obviously stupid. :)
> >
> > I have an ARM-based Intel IXP400 system with more than 64MB RAM and with an
> > Atheros AR9160 on the PCI bus (only thing on the PCI bus). ?I was able to
> > use this device with Linux 2.6.21 and an earlier driver version. ?It seemed
> > to work okay, as both client and AP. ?Now I'd like to upgrade to a newer
> > kernel and WiFi driver. ?I'm having problems getting it to work correctly.
> >
> > I am seeing a number of problems, perhaps related:
> >
> > 1.) I am seeing these warning messages:
> >
> > WARNING: at
> > /home/bp/compat-wireless-2010-12-07/drivers/net/wireless/ath/ath9k/recv.c:532
> > ath_stoprecv+0x84/0x94 [ath9k]() Could not stop RX, we could be confusing
> > the DMA engine when we start RX up
> 
> Its a generic issue in ath9k and every one gets this warning.

"Generic" implies this is known, but it is not, and each case
should be investigated. With future kernels we'll only warn
once now and only if you have developer debug config options
enabled, but we should definitely fix these.

  Luis

  reply	other threads:[~2010-12-10 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 20:44 Problems with ath9k on IXP400, using Linux 2.6.35.8 and compat-wireless-2010-12-07 B. James Phillippe
2010-12-10  7:48 ` [ath9k-devel] " Mohammed Shafi
2010-12-10 16:07   ` Luis R. Rodriguez [this message]
2010-12-11 10:02     ` Mohammed Shafi

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=20101210160702.GC2102@tux \
    --to=lrodriguez@atheros.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 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.