From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: General firmware stability issue.
Date: Thu, 19 Jun 2014 11:58:47 -0700 [thread overview]
Message-ID: <53A332E7.2060400@candelatech.com> (raw)
When using our firmware and kernel mods, we often see our AP system
crash the firmware after several days of various testing.
Often after this, it takes a full reboot to bring the system back.
For those with ability to debug firmware source,
at least some of the time, it is a heap list corruption/assert
that crashes us, but I have not nailed down exactly where/why yet.
Based on some email I received, I believe this problem may
happen on standard firmware as well.
I am curious to know if anyone else sees this type of problem,
and with what regularity.
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
next reply other threads:[~2014-06-19 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 18:58 Ben Greear [this message]
2014-06-23 6:49 ` General firmware stability issue Michal Kazior
2014-06-23 16:05 ` Ben Greear
2014-06-23 20:48 ` Ben Greear
2014-06-24 5:32 ` Michal Kazior
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=53A332E7.2060400@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox