From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Ben Greear <greearb@candelatech.com>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: FYI: msdu-desc must be multiple of 8.
Date: Tue, 27 May 2014 12:45:24 +0300 [thread overview]
Message-ID: <87bnujblmz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAHqTa-3xqtoU+hTazpRJZCMQX27Uyyi0HFjkJ9LvrGCd2Mv4vg@mail.gmail.com> (Avery Pennarun's message of "Tue, 13 May 2014 20:17:55 -0400")
Avery Pennarun <apenwarr@gmail.com> writes:
> On Tue, May 13, 2014 at 6:50 PM, Ben Greear <greearb@candelatech.com> wrote:
>> As an aside, if you do manage to crash firmware in this manner, it also
>> takes down the host when it tries to clean up the stale tx buffers. Possibly
>> that bug is just due to some of my own patches, but might be worth investigating
>> some day when I have more time and a cleaner tree...
>
> At least on my boxes, firmware crashes lead to kernel panics pretty
> often, say 1/3 of the time. There appear to be lots of ways the
> cleanups are still not happening properly on a firmware crash.
I just merged a patch from Michal which I think is related:
7147a13135ee ath10k: protect src_ring state with ce_lock in tx_sg()
Did that help? If not, any chance to get more info? I know these kind of
crashes don't usually provide much information, but even small hints
help.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-05-27 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 22:34 FYI: msdu-desc must be multiple of 8 Ben Greear
2014-05-13 22:42 ` Avery Pennarun
2014-05-13 22:50 ` Ben Greear
2014-05-14 0:17 ` Avery Pennarun
2014-05-27 9:45 ` Kalle Valo [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=87bnujblmz.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=apenwarr@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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.