ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Firmware crash when sending large numbers of forwarded packets
Date: Sat, 8 Mar 2014 10:03:31 +0200	[thread overview]
Message-ID: <87iorpnmlo.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAHqTa-2NASvnpURqH=LbPMOi8GKHB23Xc3pxwULqnsXMrKHpow@mail.gmail.com> (Avery Pennarun's message of "Fri, 7 Mar 2014 05:38:07 -0500")

Hi Avery,

Avery Pennarun <apenwarr@gmail.com> writes:

> I'm having a problem where if I transmit too fast out the ath10k
> interface in AP mode, I get a near-immediate firmware crash.

[...]

> Versions:
> - kernel is based on current kvalo/for-linville branch (should I try
> something else?) but seems to be the same in linux-next-20140114 so I
> don't think this behaviour has changed lately.

I do not recommend using for-linville branch for anything. As the name
implies, it's only for John Linville to pull ath10k and ath6kl changes
to his tree.

What I recommend is to use the master branch of my ath.git tree. That's
fairly recent wireless-testing (max 2 weeks old) plus latest ath10k +
ath6kl patches I have (ie. merge of wireless-testing and my ath-next
branch).

But if you prefer to have clean history (which wireless-testing doesn't
have), you can also use ath-next branch directly. That contains the
patches which I'm planning to send Linville next.

I wrote some documentation about branches here:

http://wireless.kernel.org/en/users/Drivers/ath10k/sources#Git_branches

But in a nutshell, use the master branch if you can. That way you are
best aligned with the ath10k developers and also spot any regressions
early on.

> - firmware version 10.1.467.2-1, but also tested with 10.1.467.1-1
> with no difference.
>
> I assume other people are not experiencing this or they would have
> mentioned it by now.  What can I do to help debug this?

We have reported the issue to the firmware team and got some feedback
already. Hopefully we know more early next week.

-- 
Kalle Valo

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

  parent reply	other threads:[~2014-03-08  8:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 10:38 Firmware crash when sending large numbers of forwarded packets Avery Pennarun
2014-03-07 11:15 ` Michal Kazior
2014-03-07 15:53 ` Ben Greear
2014-03-08  0:54   ` Avery Pennarun
2014-03-08  1:08     ` Ben Greear
2014-03-08  1:21       ` Avery Pennarun
2014-03-10  7:47     ` Michal Kazior
2014-03-08  8:03 ` Kalle Valo [this message]
2014-03-08  8:20   ` Avery Pennarun
2014-03-08 16:57     ` Kalle Valo
2014-03-10 19:26       ` Avery Pennarun
2014-03-11  7:31         ` Kalle Valo
2014-03-10 10:10     ` Michal Kazior
2014-03-10 10:16       ` Michal Kazior
2014-05-12  1:43         ` Avery Pennarun

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=87iorpnmlo.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=apenwarr@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox