All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Pushpal Sidhu <psidhu@gateworks.com>
Cc: ath10k@lists.infradead.org
Subject: Re: Timeout Issues
Date: Wed, 20 Aug 2014 08:50:37 +0300	[thread overview]
Message-ID: <87vbpn7lqq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAD1M062MNW7y_hf+5btNA14xt9K69TqQy=Q-rCm+2xuHCZDEsA@mail.gmail.com> (Pushpal Sidhu's message of "Tue, 19 Aug 2014 11:27:23 -0700")

Pushpal Sidhu <psidhu@gateworks.com> writes:

> I'm having issues with ath10k timing out when trying to communicate
> with the wireless card (UNEX DAXA-O1 + have tried several others).
> Below is what I grabbed from dmesg.
>
> $ dmesg | grep ath10k
> [    5.233469] ath10k_pci 0000:09:00.0: enabling device (0140 -> 0142)
> [    5.575954] ath10k: pci irq legacy irq_mode 0 reset_mode 0
> [    7.704403] ath10k: failed to receive control response completion, polling..
> [    8.704379] ath10k: Service connect timeout: -110
> [    8.709089] ath10k: failed to connect htt (-110)
> [    9.020495] ath10k: could not init core (-110)
> [    9.324371] ath10k: could not probe fw (-110)
>
> This causes the card to not be registered, and thus is unusable (there
> is no wlanX)

My first guess is a problem related with the PCI bus, but that's just a
guess. Can you get us a trace-cmd log:

http://wireless.kernel.org/en/users/Drivers/ath10k/debug#Tracing

> I am able to use the Intel 7260 card (another AC card) with their
> firmware binary blob, so I don't believe this is a hardware
> configuration issue with mini-pcie.

Did you try iwlwifi on the exact same kernel?

> I am using the following software on an ARM board:
> ath10k branch of linux kernel: 3.16.0-wl-ath-182333-g6a69f0c

Have you verified that with this kernel version the PCI bus works
correctly on your ARM board? Especially check that interrupts work.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2014-08-20  5:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 18:27 Timeout Issues Pushpal Sidhu
2014-08-19 18:42 ` Ben Greear
2014-08-19 21:33   ` Pushpal Sidhu
2014-08-20  5:40     ` Kalle Valo
2014-08-20  6:48       ` Michal Kazior
2014-09-02 18:51         ` Pushpal Sidhu
2014-09-02 19:16           ` Adrian Chadd
2014-09-04  8:16           ` Michal Kazior
2014-08-20  5:50 ` Kalle Valo [this message]
2014-08-20  6:00   ` Kalle Valo
2014-08-20  6:10 ` Michal Kazior

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=87vbpn7lqq.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=psidhu@gateworks.com \
    /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.