From: "Toralf Förster" <toralf.foerster@gmx.de>
To: David Rientjes <rientjes@google.com>,
David Rientjes <rientjes@google.com>
Cc: werner <w.landgraf@ru.ru>, "Wey-Yi Guy" <wey-yi.w.guy@intel.com>,
ilw@linux.intel.com, linux-wireless@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 09:31:58 +0200 [thread overview]
Message-ID: <201110170931.59534.toralf.foerster@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1110151416360.15894@chino.kir.corp.google.com>
David Rientjes wrote at 23:21:59
> What's the last kernel prior to 3.1-rc9 that worked for you?
2.6.39.4 (in general that kernel version rocks, reliable, stable, no problems
AFAICS, 3.0.x have problems in the DVB-T area, 3.1 added wlan issues)
> What does "iwconfig" show?
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=49/70 Signal level=-61 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> What does "dmesg | grep iwlagn" show?
n22 ~ # dmesg | grep iwlagn
iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:03:00.0: setting latency timer to 64
iwlagn 0000:03:00.0: pci_resource_len = 0x00002000
iwlagn 0000:03:00.0: pci_resource_base = f81f8000
iwlagn 0000:03:00.0: HW Revision ID = 0x0
iwlagn 0000:03:00.0: irq 48 for MSI/MSI-X
iwlagn 0000:03:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
iwlagn 0000:03:00.0: L1 Disabled; Enabling L0S
iwlagn 0000:03:00.0: device EEPROM VER=0x11e, CALIB=0x4
iwlagn 0000:03:00.0: Device SKU: 0Xf0
iwlagn 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
iwlagn 0000:03:00.0: loaded firmware version 8.83.5.1 build 33692
iwlagn 0000:03:00.0: L1 Disabled; Enabling L0S
iwlagn 0000:03:00.0: Radio type=0x1-0x2-0x0
iwlagn 0000:03:00.0: L1 Disabled; Enabling L0S
iwlagn 0000:03:00.0: Radio type=0x1-0x2-0x0
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
next prev parent reply other threads:[~2011-10-17 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 19:19 Toralf Förster
2011-10-15 21:21 ` David Rientjes
2011-10-17 7:31 ` Toralf Förster [this message]
2011-10-17 7:52 ` Toralf Förster
2011-10-17 14:04 ` Guy, Wey-Yi
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
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=201110170931.59534.toralf.foerster@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rientjes@google.com \
--cc=w.landgraf@ru.ru \
--cc=wey-yi.w.guy@intel.com \
/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
all inboxes | Powered by JetHome®