From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Re: Repeatable crash of CT firmware (at least).
Date: Mon, 10 Aug 2015 17:08:03 -0700 [thread overview]
Message-ID: <55C93CE3.6070306@candelatech.com> (raw)
In-Reply-To: <55C3B297.2050704@candelatech.com>
As an update, stock upstream kernels and multiple different official firmware versions
crash as well.
I've sent more details off to those that might be able to fix
things.
Thanks,
Ben
On 08/06/2015 12:16 PM, Ben Greear wrote:
> In case someone has time an interest, I would be curious if upstream
> firmware/kernels see this problem. Unfortunately, it takes a bit of
> setup to do this test (namely, constant tx source, and if doing this with
> something like ath9k, then you might need a variable attenuator).
>
> Possibly just a very loud constant tx source would reproduce the bug
> as well, and possibly it would happen in AP mode, etc.
>
> Channel 1, HT40
>
> Configure ath10k in station mode, associate with ath10k AP,
> start transmitting frames (about 4kpps tx, 1kpps rx in my case)
>
> Add a constant-transmit noise source at around -65 db on the same channel. This should
> cause ath10k station (and AP) to go silent.
>
> Shortly after, the station system's ath10k firmware crashes due to assert
> in the firmware CE logic.
>
> I know that a similar CE assert can happen if the host does bad things
> with the tx descriptors, so I am suspicious that is the case here. For instance,
> maybe firmware is still trying to transmit the frame when host tears down
> the station vdev??
>
> Of course, this could all be due to bugs in CT firmware and/or my kernel
> patches...
>
> 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
prev parent reply other threads:[~2015-08-11 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 19:16 Repeatable crash of CT firmware (at least) Ben Greear
2015-08-11 0:08 ` Ben Greear [this message]
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=55C93CE3.6070306@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.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.