Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@sig21.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k_htc: Target is unresponsive
Date: Fri, 17 May 2013 08:00:42 +0200	[thread overview]
Message-ID: <20130517060042.GA21663@sig21.net> (raw)
In-Reply-To: <20130516234526.GH3795@alittletooquiet.net>

On Thu, May 16, 2013 at 07:45:26PM -0400, Forest Bond wrote:
> On Fri, May 17, 2013 at 01:48:57AM +0200, Ignacy Gawedzki wrote:
> > On Thu, May 16, 2013 at 08:50:30PM +0200, thus spake Ignacy Gawedzki:
> > > I'll try on yet another one and will tell you the results.
> > 
> > Just tried on ICH7, same thing.  The easiest way to reproduce the bug is to
> > boot into single user mode ("recovery mode" on Ubuntu), in order to prevent
> > any NetworkManager or udev from interfering.  Then, without any attempt to up
> > the interface, reboot the system by typing "reboot" in a root shell.
> 
> FWIW, this has also been a problem for me on Ubuntu 12.04.  I can reproduce it
> the same way.

FWIW, I also met this problem after I added ath9k_htc
to my initrd (via /etc/initramfs-tools/modules).
So I removed it and the issue went away.  I first
noticed it after resume from suspend-to-disk, but
later found it doesn't work after warm reboot, too.
The mainboard has Intel H77 chipset, the TL-WN722N is
plugged into USB2.0 port.


Johannes

  reply	other threads:[~2013-05-17  6:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 13:42 [ath9k-devel] ath9k_htc: Target is unresponsive Ignacy Gawedzki
2013-05-15 14:43 ` Eugene Krasnikov
2013-05-15 14:50 ` Kalle Valo
2013-05-15 16:11   ` Eugene Krasnikov
2013-05-15 16:34     ` Ignacy Gawedzki
2013-05-16 13:27 ` Oleksij Rempel
2013-05-16 17:20   ` Ignacy Gawedzki
2013-05-16 17:46     ` Oleksij Rempel
2013-05-16 18:50       ` Ignacy Gawedzki
2013-05-16 23:48         ` Ignacy Gawedzki
2013-05-16 23:45           ` Forest Bond
2013-05-17  6:00             ` Johannes Stezenbach [this message]
2013-05-17  8:07               ` Oleksij Rempel
2013-05-17  8:15                 ` Ignacy Gawedzki
2013-05-17  8:31                   ` Oleksij Rempel
2013-05-17  9:33                     ` Eugene Krasnikov
2013-05-17 10:30                       ` Ignacy Gawedzki
2013-05-17 10:40                         ` Ignacy Gawedzki
2013-05-17 10:48                           ` Oleksij Rempel
2013-05-17 11:22                             ` Ignacy Gawedzki
2013-05-17 11:41                               ` Ignacy Gawedzki
2013-05-17 12:00                                 ` Oleksij Rempel
2013-05-17 15:37                                   ` Adrian Chadd
2013-05-17 18:51                                     ` Oleksij Rempel
2013-05-18 10:59                                       ` Oleksij Rempel
  -- strict thread matches above, loose matches on Subject: below --
2013-11-13 11:23 Rajeshwar Bandi
2013-11-13 14:39 ` Oleksij Rempel

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=20130517060042.GA21663@sig21.net \
    --to=js@sig21.net \
    --cc=ath9k-devel@lists.ath9k.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