From: Adam Baker <linux@baker-net.org.uk>
To: Anders Eriksson <aeriksson@fastmail.fm>
Cc: linux-wireless@vger.kernel.org, rt2400-devel@lists.sourceforge.net
Subject: Re: [Rt2400-devel] No ProbeResp == dead interface?
Date: Thu, 19 Mar 2009 21:56:55 +0000 [thread overview]
Message-ID: <200903192156.55843.linux@baker-net.org.uk> (raw)
In-Reply-To: <20090308162023.BBD122C40D0@tippex.mynet.homeunix.org>
On Sunday 08 March 2009, Anders Eriksson wrote:
> So,
> Now it has happened again. :-(
>
> I can conclude that a rmmod/modprobe cycle does not help.
>
Well I can see from those logs that it is only the transmit side that is
failing, some traffic is being seen on the receive side.
Does your hardware have an rfkill button and do you have rfkill support
enabled? I'm wondering if rfkill could be activated by a glitch on the
signal.
Other than that this is going to be tricky to do anything with. The fact that
rmmod doesn't help suggests that there is a reasonable possibility of this
being a hardware issue that the software can't fix (assuming this is a rt2500
issue, not something deeper in the stack). You can't do any very intrusive
monitoring as the system needs to be left too long before it fails, except
possibly by rmmodding the original driver when it fails and insmodding a new
one that contains lots of printk statements in the tx path to see which het
triggered. If trying that approach don't forget to instrument
rt2500pci_interrupt as well as rt2x00mac_tx
Adam
next prev parent reply other threads:[~2009-03-19 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 20:58 No ProbeResp == dead interface? Anders Eriksson
2009-02-19 23:16 ` [Rt2400-devel] " Adam Baker
2009-02-20 7:47 ` Anders Eriksson
2009-02-20 23:07 ` Adam Baker
2009-02-21 14:55 ` Anders Eriksson
2009-02-21 21:23 ` Adam Baker
2009-03-08 16:20 ` Anders Eriksson
2009-03-19 21:56 ` Adam Baker [this message]
2009-03-20 6:31 ` Anders Eriksson
2009-03-31 18:17 ` Anders Eriksson
-- strict thread matches above, loose matches on Subject: below --
2009-03-18 14:45 aeriksson2
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=200903192156.55843.linux@baker-net.org.uk \
--to=linux@baker-net.org.uk \
--cc=aeriksson@fastmail.fm \
--cc=linux-wireless@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/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).