From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: David Rientjes <rientjes@google.com>, werner <w.landgraf@ru.ru>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 3.1.0-rc9+ : wlan stops working w/o any error messages
Date: Mon, 17 Oct 2011 07:04:06 -0700 [thread overview]
Message-ID: <1318860246.31823.33.camel@wwguy-huron> (raw)
In-Reply-To: <201110170952.43916.toralf.foerster@gmx.de>
On Mon, 2011-10-17 at 00:52 -0700, Toralf Förster wrote:
> Toralf Förster wrote at 09:31:58
> > > What does "iwconfig" show?
>
> And this is the state if the netwerk stops working :
>
> wlan0 IEEE 802.11abgn ESSID:"IBM"
> Mode:Managed Frequency:2.462 GHz Access Point: 00:21:55:AC:8B:80
> Bit Rate=54 Mb/s Tx-Power=15 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality=45/70 Signal level=-65 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:77 Missed beacon:0
>
>
when you say "stop working", but it is still associated, correct? just
no traffic get through.
Thanks
Wey
next prev parent reply other threads:[~2011-10-17 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201110152119.58509.toralf.foerster@gmx.de>
2011-10-15 21:21 ` 3.1.0-rc9+ : wlan stops working w/o any error messages David Rientjes
2011-10-17 7:31 ` Toralf Förster
2011-10-17 7:52 ` Toralf Förster
2011-10-17 14:04 ` Guy, Wey-Yi [this message]
2011-10-17 17:06 ` Toralf Förster
2011-10-17 19:30 ` wwguy
2011-10-18 16:47 ` Toralf Förster
2011-10-18 17:13 ` wwguy
2011-10-18 17:57 ` Toralf Förster
2011-10-18 17:51 ` Guy, Wey-Yi
2011-10-19 11:01 ` Toralf Förster
2011-10-19 13:49 ` Guy, Wey-Yi
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=1318860246.31823.33.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rientjes@google.com \
--cc=toralf.foerster@gmx.de \
--cc=w.landgraf@ru.ru \
/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).