linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [WEXT]: multiple calls for SIOCGIWSTATS return same value
Date: Tue, 09 Jun 2015 09:33:08 +0200	[thread overview]
Message-ID: <1433835188.1892.5.camel@sipsolutions.net> (raw)
In-Reply-To: <20150608195853.239a2622@erg.abdn.ac.uk>

On Mon, 2015-06-08 at 19:58 -0600, Gerrit Renker wrote:

> I am primarily referring to the signal level. The first call returns a
> plausible value e.g. -78dB. All subsequent calls return the same value,
> regardless of receiver position (moving the laptop).
> 
> It almost looks like a static value that gets initialized and then 
> does not change.
> 
> There is a similar behaviour for scan results: the signal levels reported
> for stations remain the same for all subsequent calls. Previously these
> also changed with time and position of receiver.

You mean BSSes, not stations, right? This is very strange - it seems
those should be two entirely different code paths in the kernel.

What driver are you using? But then again, you said nl80211/iw works,
right? Then the driver shouldn't matter.

Do you think you'd be able to use tracing?

trace-cmd report -e cfg80211 -e mac80211

would report the calls to/from the driver and could perhaps shed some
light. If you can record this, send me the resulting trace.dat file
(compressed) off-list.

johannes


  reply	other threads:[~2015-06-09  7:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-07  2:37 [WEXT]: multiple calls for SIOCGIWSTATS return same value Gerrit Renker
2015-06-08  7:18 ` Johannes Berg
2015-06-09  1:58   ` Gerrit Renker
2015-06-09  7:33     ` Johannes Berg [this message]
2015-06-10  2:25       ` Gerrit Renker
2015-06-10  6:12         ` Johannes Berg

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=1433835188.1892.5.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=gerrit@erg.abdn.ac.uk \
    --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).