ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Pushpal Sidhu <psidhu@gateworks.com>
Cc: ath10k@lists.infradead.org
Subject: Re: Timeout Issues
Date: Tue, 19 Aug 2014 11:42:59 -0700	[thread overview]
Message-ID: <53F39AB3.10601@candelatech.com> (raw)
In-Reply-To: <CAD1M062MNW7y_hf+5btNA14xt9K69TqQy=Q-rCm+2xuHCZDEsA@mail.gmail.com>

On 08/19/2014 11:27 AM, Pushpal Sidhu wrote:
> Hi,
> 
> I'm having issues with ath10k timing out when trying to communicate
> with the wireless card (UNEX DAXA-O1 + have tried several others).

Have you tried a WLE900 VX NIC?  Those have worked well for me.


> 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)
> 
> 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.
> 
> I am using the following software on an ARM board:
> ath10k branch of linux kernel: 3.16.0-wl-ath-182333-g6a69f0c
> latest git of hostapd
> latest git of iw
> latest git of wpa_supplicant
> 
> I have tried both firmware-2 binary blobs (the "AP" and "STA"
> versions) as well as the newer firmware-3 binary with the same exact
> messages being displayed.
> 
> Any help towards finding a solution is appreciated, thanks!

Probably this is not a firmware issue, but if you have nothing else
to try, you can try my version of the 10.1.x firmware:

http://www.candelatech.com/ath10k.php

and possibly my hacked 3.14.14 kernel, which may spew out some additional
debug info if you have something like OTP issues.

git clone git://dmz2.candelatech.com/linux-3.14.dev.y

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


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

  reply	other threads:[~2014-08-19 18:43 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 [this message]
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
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=53F39AB3.10601@candelatech.com \
    --to=greearb@candelatech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox