All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Card AR928X very slow with new kernels
Date: Mon, 23 Apr 2012 03:39:57 +0200	[thread overview]
Message-ID: <20120423013957.5007.qmail@stuge.se> (raw)
In-Reply-To: <CABg7HFOtt2b7bmbBODjHcfotAakVsokBmB6HeQ3m3ZVkovD3wQ@mail.gmail.com>

Mitch Davis wrote:
> I'd love to investigate what's happening but I have no idea where
> to start.  Is this page what I'm after:
> 
>   http://linuxwireless.org/en/users/Drivers/ath9k/debug
> 
> That page tells me about all the cool things for debugging, but
> doesn't give me an idea of how to methodically go about finding the
> right info.  Any suggestions for values of debug?  Any suggestions
> for the right place to look in /sys/kernel/debug/ath9k?

I was in your situation some years ago. Unfortunately what you hope
for is nowhere to be found. :\

If you want someone knowledgeable about ath9k hardware to talk in
deep technical detail with you then you must basically first prove
yourself by studying the driver enough that you can actually fix the
problem on your own. You will unfortunately find little to no help
with loading the driver into your head, not even some simple overview
like "it's like NIC with x tx descriptors and y rx descriptors". :\
The data sheet for the hardware is not generally available. It has
leaked of course, but you are discouraged to use it unless you have
received your own copy off-list thanks to your outstanding efforts.

Atheros try to take problem reports seriously and will try to
reproduce problems in their lab. If they succeed they typically
develop fixes. I have yet to see Atheros guide any user on the list,
competent as she may be, to do remote debugging to find the key
information about the error in the local environment where the error
is reliably reproducible. I have ranted violently about this on the
list and many people hate me for that.

Obviously your problem is often not reproducible in the lab, because
it depends on factors in your RF environment, which I assume that
everyone understands. I'm not completely sure about the reasons for
this sad state of affairs, but that's the way it goes here. :\


//Peter

  reply	other threads:[~2012-04-23  1:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22  0:54 [ath9k-devel] Card AR928X very slow with new kernels Pierre Willaime
2012-04-22 23:45 ` Mitch Davis
2012-04-23  1:39   ` Peter Stuge [this message]
2012-04-23  2:35     ` Mitch Davis
2012-04-23  3:07       ` Ben Greear
2012-04-23  3:16       ` Peter Stuge
2012-04-23  6:58         ` Mitch Davis
2012-04-23 12:47           ` Peter Stuge
2012-04-23 12:54             ` Mitch Davis
2012-04-23 13:46           ` Ben Greear
2012-04-23 14:50             ` Ben Greear

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=20120423013957.5007.qmail@stuge.se \
    --to=peter@stuge.se \
    --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.