From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [WEXT]: multiple calls for SIOCGIWSTATS return same value
Date: Mon, 8 Jun 2015 19:58:53 -0600 [thread overview]
Message-ID: <20150608195853.239a2622@erg.abdn.ac.uk> (raw)
In-Reply-To: <1433747886.2106.5.camel@sipsolutions.net>
> On Sat, 2015-06-06 at 20:37 -0600, Gerrit Renker wrote:
> > A problem has been found in recent kernels where multiple
> > calls using SIOCGIWSTATS return the same, identical value.
>
> Which "value"? I believe these return a number of different values. What
> are the returned values? Are they perhaps just 0?
>
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.
> Is the application a 32-bit application running on a 64-bit machine
> perhaps?
Sorry forgot to mention: application and operating system both 64 bit,
the bug submitted to wavemon also mentioned 64 bit.
Thank you for the reply -- maybe this means that the root cause is in a
different part; I would not know which at the moment.
next prev parent reply other threads:[~2015-06-09 1:59 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 [this message]
2015-06-09 7:33 ` Johannes Berg
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=20150608195853.239a2622@erg.abdn.ac.uk \
--to=gerrit@erg.abdn.ac.uk \
--cc=johannes@sipsolutions.net \
--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).