From: David Madore <david+ml@madore.org>
To: Adrian Chadd <adrian@freebsd.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath9k_htc fails with "Target is unresponsive"
Date: Thu, 22 Mar 2012 01:29:55 +0100 [thread overview]
Message-ID: <20120322002955.GA9391@aldebaran.gro-tsen.net> (raw)
In-Reply-To: <20120321220242.GA26363@aldebaran.gro-tsen.net>
On Wed, Mar 21, 2012 at 11:02:42PM +0100, David Madore wrote:
> Or, to summarize all of this: the dongle works if and only if
> ath9k_htc is initializing it for the very first time since it was
> physically plugged in or powered on. No reset, USB reset or software
> reset of any kind seems to help.
More accurately: the dongle fails to work if and only if, since it was
last plugged in, there has been a reboot (=anything short of a full
power cycle) after it has been initialized by ath9k_htc.
Unloading and reloading the kernel modules does not cause a failure
(but neither does it solve the problem). Rebooting[#] the machine
causes the problem if and only if ath9k_htc has been loaded prior to
reboot (even if there have been other intermediate reboots). Powering
the machine down, or unplugging the dongle, are the only way I've
found of restoring a sane state: no lesser kind of USB reset has
worked.
[#] I should try kexec, but I haven't been able to get it to work.
I'm willing to run any other experience which might elucidate things,
of course.
--
David A. Madore
( http://www.madore.org/~david/ )
next prev parent reply other threads:[~2012-03-22 0:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 17:58 ath9k_htc fails with "Target is unresponsive" David Madore
2012-03-21 20:16 ` Adrian Chadd
2012-03-21 22:02 ` David Madore
2012-03-22 0:29 ` David Madore [this message]
2012-03-22 4:50 ` Adrian Chadd
2012-03-23 3:44 ` Sujith Manoharan
2012-03-23 17:47 ` David Madore
2012-03-27 8:29 ` Sujith Manoharan
2012-05-11 19:47 ` ath9k_htc fails with Robert Bouterse
2012-05-14 9:19 ` Sujith Manoharan
2012-05-14 22:23 ` Bouterse, Robert
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=20120322002955.GA9391@aldebaran.gro-tsen.net \
--to=david+ml@madore.org \
--cc=adrian@freebsd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.