All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k_htc: Target is unresponsive
Date: Fri, 17 May 2013 10:31:28 +0200	[thread overview]
Message-ID: <5195EAE0.7040403@rempel-privat.de> (raw)
In-Reply-To: <20130517081507.GA9673@zenon.in.qult.net>

Am 17.05.2013 10:15, schrieb Ignacy Gawedzki:
> On Fri, May 17, 2013 at 10:07:00AM +0200, thus spake Oleksij Rempel:
>> OK, now i was able to reproduce it on ar9271.
>
> Ah, good, but what did you do wrong previously then?

Nothing. I needed to start single user mode first, and reboot the system 
to et this error.

>
>> In attachment is the log i grubbed form adapter.
>> Lines starting with ######### are my comments
>
> At least we can already diagnose a problem with A_PRINTF. :/
>
> Do these logs speak to anyone?
>

Here are some explanations:
"ASIC-ROM_1.8" - is start of boot loader on device. It should go 
immediately after adapter got power.
"8. download" - at this stage bootloader is ready to receive firmware.
"[Tgt running" - firmware was downloaded and running.
"!USB suspend" - means usb suspend was initiated
And that is probably our problem.

-- 
Regards,
Oleksij

  reply	other threads:[~2013-05-17  8:31 UTC|newest]

Thread overview: 39+ 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 13:42 ` Ignacy Gawedzki
2013-05-15 14:43 ` [ath9k-devel] " Eugene Krasnikov
2013-05-15 14:43   ` Eugene Krasnikov
2013-05-15 14:50 ` Kalle Valo
2013-05-15 14:50   ` Kalle Valo
2013-05-15 16:11   ` Eugene Krasnikov
2013-05-15 16:11     ` Eugene Krasnikov
2013-05-15 16:34     ` Ignacy Gawedzki
2013-05-15 16:34       ` Ignacy Gawedzki
2013-05-16 13:27 ` Oleksij Rempel
2013-05-16 13:27   ` Oleksij Rempel
2013-05-16 17:20   ` Ignacy Gawedzki
2013-05-16 17:20     ` Ignacy Gawedzki
2013-05-16 17:46     ` Oleksij Rempel
2013-05-16 17:46       ` Oleksij Rempel
2013-05-16 18:50       ` Ignacy Gawedzki
2013-05-16 18:50         ` Ignacy Gawedzki
2013-05-16 23:48         ` Ignacy Gawedzki
2013-05-16 23:48           ` Ignacy Gawedzki
2013-05-16 23:45           ` Forest Bond
2013-05-16 23:45             ` Forest Bond
2013-05-17  6:00             ` Johannes Stezenbach
2013-05-17  6:00               ` Johannes Stezenbach
2013-05-17  8:07               ` Oleksij Rempel
2013-05-17  8:15                 ` Ignacy Gawedzki
2013-05-17  8:31                   ` Oleksij Rempel [this message]
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=5195EAE0.7040403@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --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 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.