From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Failure to allocate large memory blocks upon firmware crash
Date: Fri, 21 Mar 2014 10:39:48 +0200 [thread overview]
Message-ID: <87y504aqsr.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAHqTa-3=VZr2-S63HXEX++Y5BvPRuUTKgB_nKhpCCUYD-nGe+A@mail.gmail.com> (Avery Pennarun's message of "Wed, 19 Mar 2014 22:42:06 -0400")
Hi Avery,
replying in smaller parts, easier to discuss that way.
Avery Pennarun <apenwarr@gmail.com> writes:
> We are still getting firmware crashes occasionally, but I haven't
> narrowed down the cause nor tried the very latest driver, so I won't
> bother you with those just yet.
Even if you are not using the latest and greatest ath10k I think you
should still post the firmware crashes. Then we can try to analyse
what's causing them.
What I'm wondering is that why you seem to have firmware crashes so
often. For example, I'm not seeing anything like that on our MIPS based
AP135 platform. Maybe there are more memory barrier issues like you
reported earlier?
What kind of platform are you using? Does it have any special
characteristics related to cache coherency, PCI access or similar?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-03-21 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 2:42 Failure to allocate large memory blocks upon firmware crash Avery Pennarun
2014-03-21 8:39 ` Kalle Valo [this message]
2014-03-21 8:54 ` Kalle Valo
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=87y504aqsr.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