From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v2] ath10k: support firmware crash-by-assert
Date: Thu, 11 Sep 2014 23:44:00 +0300 [thread overview]
Message-ID: <87vbot28hb.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20140910155928.30418.45160.stgit@potku.adurom.net> (Kalle Valo's message of "Wed, 10 Sep 2014 18:59:28 +0300")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> From: Ben Greear <greearb@candelatech.com>
>
> 10.1 firmware does not have an official way to
> cause assert on purpose, but it can be done with
> carefully crafted WMI command. This is a different
> kind of crash from the 'hard' crash, which is
> a bad memory dereference.
>
> Different crashes decode in different manners, so
> this will help the crash-report testing as well as
> offer better ways to test firmware failure and
> recovery.
>
> kvalo: move the wmi command creation to debug.c, modify
> the info print
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Thanks Ben, applied.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] ath10k: support firmware crash-by-assert
Date: Thu, 11 Sep 2014 23:44:00 +0300 [thread overview]
Message-ID: <87vbot28hb.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20140910155928.30418.45160.stgit@potku.adurom.net> (Kalle Valo's message of "Wed, 10 Sep 2014 18:59:28 +0300")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> From: Ben Greear <greearb@candelatech.com>
>
> 10.1 firmware does not have an official way to
> cause assert on purpose, but it can be done with
> carefully crafted WMI command. This is a different
> kind of crash from the 'hard' crash, which is
> a bad memory dereference.
>
> Different crashes decode in different manners, so
> this will help the crash-report testing as well as
> offer better ways to test firmware failure and
> recovery.
>
> kvalo: move the wmi command creation to debug.c, modify
> the info print
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Thanks Ben, applied.
--
Kalle Valo
next prev parent reply other threads:[~2014-09-11 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 15:59 [PATCH v2] ath10k: support firmware crash-by-assert Kalle Valo
2014-09-10 15:59 ` Kalle Valo
2014-09-10 16:34 ` Ben Greear
2014-09-10 16:34 ` Ben Greear
2014-09-11 20:40 ` Kalle Valo
2014-09-11 20:40 ` Kalle Valo
2014-09-11 20:44 ` Kalle Valo [this message]
2014-09-11 20:44 ` 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=87vbot28hb.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.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 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.