From: Ben Greear <greearb@candelatech.com>
To: Venkat Ch <venkatch@gmail.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Tips to debug Firmware crash
Date: Mon, 27 Apr 2015 07:17:13 -0700 [thread overview]
Message-ID: <553E44E9.7020007@candelatech.com> (raw)
In-Reply-To: <CABHL29Hq8e+sgyfqtN-EbEpM1cC9XF_bO3F_rj68Piq-kKg4=w@mail.gmail.com>
On 04/26/2015 10:48 PM, Venkat Ch wrote:
> Hi All,
>
> I am an active developer of Atheros drivers for the last 10 years. I
> have been working on QCA 10.2.2 driver for the last few months and
> trying to understand the architecture of this offloading model. Though
> this forum is nothing to do with Atheros provided drivers, I took the
> liberty of posting the question to see if Ath10k community could help
> me. Sorry if I violated any guidelines.
>
> There is some problem at firmware level about which I am clueless.
> Whenever there is a crash in firmware the 5GHz interface goes down
> completely and there will not be any transmissions or receptions from
> the interface from then. What all I see on the console is some log
> message "Target Asserted" . I don't get any stack trace to see in
> which function it crashed.
>
> Can any of you please let me know if there is a way to dump the stack
> trace and debug the firmware crash?
I have tools to debug my modified 10.1 'CT' firmware and get backtraces and decode
the log messages and such. I can't publish the details due to NDA, but I can
give vague descriptions of the problem and usually figure out a way to fix it.
For 10.2, you would need to talk to someone with that firmware source code,
as I have not been given access to it.
Thanks,
Ben
>
>
> Thanks & Regards
> Venkat
>
>
--
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-04-27 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 5:48 Tips to debug Firmware crash Venkat Ch
2015-04-27 14:17 ` 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=553E44E9.7020007@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=venkatch@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox