linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: 31-rc3-mmotm0716 - wonky wireless statistics..
Date: Wed, 29 Jul 2009 09:31:18 +0800	[thread overview]
Message-ID: <1248831078.3747.1117.camel@debian> (raw)
In-Reply-To: <5934.1248814870@turing-police.cc.vt.edu>

On Wed, 2009-07-29 at 05:01 +0800, Valdis.Kletnieks@vt.edu wrote:
> Dell Latitude D820 laptop, lspci reports the network card as:
> 
> 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Netwo           rk Connection (rev 02)
> 
> iwlwifi driver in use, card associated via wpa_supplicant but not being
> actively used
> 
> # iwconfig
> wlan0     IEEE 802.11abg  ESSID:"VT-Wireless"  
>           Mode:Managed  Frequency:2.447 GHz  Access Point: 00:11:20:A4:4C:10   
>           Bit Rate=54 Mb/s   Tx-Power=15 dBm   
>           Retry  long limit:7   RTS thr:off   Fragment thr:off
>           Encryption key:<lopped out> [2]
>           Link Quality=62/70  Signal level=-48 dBm  
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> # cat /proc/net/wireless
> Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
>  face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22
>  wlan0: 0000   63.  -47.  -256        0      0      0      0      0        0
>  wlan1: 0000    0     0     0        0      0      0      0      0        0
>  wlan2: 0000    0     0     0        0      0      0      0      0        0
> 
> Where did that -256 for "noise" come from?  It ends up confusing the
> gkrellm-wifi plugin, it reports a S/N of 219dB ;)

This should be related to http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commit;h=fdb897ea5c77836f890033d563336ab0c94c9222

But I don't think this is an ABI broken. User space should parse the
trailing '.' to see if a field is updated or not because there are cards
not capable to report hardware noise level anyway. Johannes?

Thanks,
-yi


  reply	other threads:[~2009-07-29  1:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 21:01 31-rc3-mmotm0716 - wonky wireless statistics Valdis.Kletnieks
2009-07-29  1:31 ` Zhu Yi [this message]
2009-07-29  7:19   ` Johannes Berg
2009-08-04  3:40     ` Valdis.Kletnieks

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=1248831078.3747.1117.camel@debian \
    --to=yi.zhu@intel.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --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).