From: James Morris <jmorris@namei.org>
To: linux-wireless@vger.kernel.org
Cc: fabrice@bellet.info
Subject: Problem with Cisco MPI350/airo
Date: Wed, 19 Sep 2007 02:22:21 -0700 (PDT) [thread overview]
Message-ID: <Xine.LNX.4.64.0709190051080.29334@us.intercode.com.au> (raw)
I've got an x31 thinkpad with an MPI350 card, which has worked more or
less reliably for several years.
With current git and Fedora kernels, the wireless dies some time after
boot, with the following types of messages ending up in syslog:
Sep 19 16:36:32 localhost kernel: airo(eth0): cmd:1 status:7f21 rsp0:21 rsp1:0 rsp2:2eab
Sep 19 16:36:32 localhost kernel: airo(eth0): Bad MAC enable reason=21, rid=0, offset=11947
Sep 19 16:36:33 localhost kernel: airo(eth0): cmd:2 status:7f02 rsp0:0 rsp1:0 rsp2:2eab
Sep 19 16:36:33 localhost kernel: airo(eth0): cmd:1 status:7f01 rsp0:2 rsp1:0 rsp2:2eab
Sep 19 16:36:33 localhost kernel: airo(eth0): Bad MAC enable reason=2, rid=0, offset=11947
Sep 19 16:36:33 localhost kernel: airo(eth0): cmd:3 status:7f03 rsp0:0 rsp1:0 rsp2:2eab
NetworkManager seems to lose contact with the card, then fails & asks for
a new key (which it doesn't actually need).
Sep 19 16:37:03 localhost NetworkManager: <info> Activation
(eth0/wireless): association took too long (>20s), asking for
new key.
Anyone seen this before, and/or know what's happening ?
- James
--
James Morris
<jmorris@namei.org>
next reply other threads:[~2007-09-19 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 9:22 James Morris [this message]
2007-09-24 11:35 ` Problem with Cisco MPI350/airo Michal Schmidt
2007-09-24 23:31 ` James Morris
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=Xine.LNX.4.64.0709190051080.29334@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=fabrice@bellet.info \
--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).