From: Ben Greear <greearb@candelatech.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>,
ath10k@lists.infradead.org, Kalle Valo <kvalo@qca.qualcomm.com>
Subject: Re: 9984 issues
Date: Mon, 25 Jul 2016 07:43:56 -0700 [thread overview]
Message-ID: <579625AC.107@candelatech.com> (raw)
In-Reply-To: <73ce025f-c583-a747-ee9a-91bbfba56ff4@dd-wrt.com>
On 07/25/2016 07:37 AM, Sebastian Gottschall wrote:
> Hello
>
> finally i received 9984 devices to follow up with my work on vht160.
> but the big issue is. the 9984 works in ap mode with current firmware. but in sta mode it crashes after seconds, no matter which operation mode is used.
> ben's ct firmware crashes in ap and sta mode, so i prefer to run using the offical variant. can someone help here?
Does it crash if you connect to an AP with 9980 or 9880? I am curious if it is only with
9984 AP that crashes. I have only one 9984 radio right now, but STA mode was working for me against
9980 AP.
I am just getting started on this, so hopefully it will get more stable soon...
And for the QCA firmware, might be worth posting a stack dump from the firmware,
maybe someone there can decode it. Unfortunately, I could not get a useful decode
from the one you sent me of my firmware...
Thanks,
Ben
>
> Sebastian
>
--
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
next prev parent reply other threads:[~2016-07-25 14:44 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 6:17 [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform Rajkumar Manoharan
2016-06-29 13:55 ` Sebastian Gottschall
2016-06-29 14:04 ` Sebastian Gottschall
2016-06-29 14:10 ` Sebastian Gottschall
2016-06-29 16:35 ` Manoharan, Rajkumar
2016-06-29 16:58 ` Sebastian Gottschall
2016-06-30 7:09 ` Michal Kazior
2016-07-19 15:25 ` Manoharan, Rajkumar
2016-07-19 16:13 ` Adrian Chadd
2016-07-19 16:53 ` Ben Greear
2016-07-19 17:00 ` Adrian Chadd
2016-07-20 5:38 ` Michal Kazior
2016-07-20 5:44 ` Adrian Chadd
2016-07-20 6:05 ` Michal Kazior
2016-07-20 6:11 ` Adrian Chadd
2016-07-20 6:27 ` Michal Kazior
2016-07-20 8:49 ` Sebastian Gottschall
2016-07-20 8:51 ` rx rate issue Sebastian Gottschall
2016-07-20 10:23 ` Michal Kazior
2016-07-20 10:50 ` Sebastian Gottschall
2016-07-20 11:03 ` Michal Kazior
2016-07-20 11:10 ` Sebastian Gottschall
2016-07-20 11:32 ` Michal Kazior
2016-07-20 11:12 ` Sebastian Gottschall
2016-07-20 16:42 ` Ben Greear
2016-07-20 16:50 ` Sebastian Gottschall
2016-07-25 14:37 ` 9984 issues Sebastian Gottschall
2016-07-25 14:43 ` Ben Greear [this message]
2016-07-25 15:09 ` Sebastian Gottschall
2016-07-25 16:03 ` Adrian Chadd
2016-07-25 16:31 ` Sebastian Gottschall
2016-07-25 17:22 ` Adrian Chadd
2016-07-26 1:11 ` Sebastian Gottschall
2016-07-26 2:26 ` Ben Greear
2016-07-26 2:40 ` Sebastian Gottschall
2016-07-26 9:31 ` 9984 issues solution Sebastian Gottschall
2016-07-26 10:27 ` Michal Kazior
[not found] ` <d5410503-fd51-5076-82 ,36-c296346f5d7f@dd-wrt.com>
[not found] ` <BAY176-W27264163A549F6C69777EFB60D0@phx.gbl>
2016-07-26 3:06 ` Not able to capture qos data packets - QCA988x sudheer thota
2016-07-26 6:21 ` Michal Kazior
2016-07-26 11:53 ` sudheer thota
[not found] ` <BAY176-W426C633D2FC24792734487B90F0@phx.gbl>
2016-07-27 6:51 ` RIFS packets missing on ath10k monitor sudheer thota
2016-07-20 17:02 ` [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform Adrian Chadd
2016-09-26 16:53 ` [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform (DMA32 issue) Ben Greear
2016-07-20 16:48 ` [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform Ben Greear
2016-07-20 5:36 ` Michal Kazior
2016-07-20 16:52 ` Ben Greear
2016-07-22 22:43 ` Ben Greear
2016-07-23 9:11 ` Sebastian Gottschall
2016-07-23 9:45 ` Manoharan, Rajkumar
2016-07-23 21:55 ` Ben Greear
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=579625AC.107@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=s.gottschall@dd-wrt.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;
as well as URLs for NNTP newsgroup(s).