Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Thomas Wagner <thomas.wagner@hs-rm.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Logging Frameconent in Interrupt Service Routine
Date: Tue, 31 Jul 2012 20:04:45 +0200	[thread overview]
Message-ID: <1497549.Eabf10WTys@buri> (raw)

Hi, 

I have some problems with the ath9k driver.
Some Wifi-frames don't aperar in the ath9k_tasklet() function.
Within this function I logged all apearing frames using printk(). I accessed the Wifi-framecontet by reading "skb->data".
I monitored on an other computer Wifi traffic using wireshark and compare frames in wireshark with the kernellog. In wireshark i saw all expected frames but in kernellog they are missed.

I would like to know how I can log the Wifi Frameconent below ath9k_tasklet(). Then I would expand my logging and follow the frames from ath_isr() to the point where they were droped.

Cheers, Tom

p.s.:
1. See this mail for deatils: "[ath9k-devel] Frames droped on Linksys WRT160NL Router"
2. This seems to be a bug,  "changed_flags" (Line 20) is  set but never read: http://is.gd/zqQirl 

                 reply	other threads:[~2012-07-31 18:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1497549.Eabf10WTys@buri \
    --to=thomas.wagner@hs-rm.de \
    --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