From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com>
Cc: "greearb@candelatech.com" <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: fix firmware assert in monitor mode
Date: Mon, 7 Mar 2016 09:51:17 +0000 [thread overview]
Message-ID: <87a8mavcoh.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1456929832-6147-1-git-send-email-rmanohar@qti.qualcomm.com> (Rajkumar Manoharan's message of "Wed, 2 Mar 2016 20:13:52 +0530")
Rajkumar Manoharan <rmanohar@qti.qualcomm.com> writes:
> commit 166de3f1895d ("ath10k: remove supported chain mask") had revealed
> an issue on monitor mode. Configuring NSS upon monitor interface
> creation is causing target assert in all qca9888x and qca6174 firmware.
> Firmware assert issue can be reproduced by below sequence even after
> reverting commit 166de3f1895d ("ath10k: remove supported chain mask").
>
> ip link set wlan0 down
> iw wlan0 set type monitor
> iw phy0 set antenna 7
> ip link set wlan0 up
>
> This issue is originally reported on qca9888 with 10.1 firmware.
>
> Fixes: 5572a95b4b ("ath10k: apply chainmask settings to vdev on creation")
> Reported-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
> Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
Applied, thanks for fixing this. I also CCed stable.
But I'm not actually sure if the "Fixes" lines implies "Cc stable"? I
think I saw one patch going into stable like that so I have been
wondering how this works. Does anyone know?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2016-03-07 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 14:43 [PATCH] ath10k: fix firmware assert in monitor mode Rajkumar Manoharan
2016-03-07 9:51 ` Valo, Kalle [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=87a8mavcoh.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 \
--cc=rmanohar@qti.qualcomm.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