From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from sabertooth01.qualcomm.com ([65.197.215.72]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1Ys9h2-0003jv-TV for ath10k@lists.infradead.org; Tue, 12 May 2015 12:53:53 +0000 From: Kalle Valo Subject: Re: Ath10 firmware crashing in Monitor mode(Sniffer mode) References: <87iobygf96.fsf@kamboji.qca.qualcomm.com> Date: Tue, 12 May 2015 15:53:22 +0300 In-Reply-To: (Michal Kazior's message of "Tue, 12 May 2015 14:34:57 +0200") Message-ID: <87bnhqgdod.fsf@kamboji.qca.qualcomm.com> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Michal Kazior Cc: linux-wireless , "ath10k@lists.infradead.org" , s prasad Michal Kazior writes: > On 12 May 2015 at 14:19, Kalle Valo wrote: >> Michal Kazior writes: >> >>> On 11 May 2015 at 23:27, s prasad wrote: >>>> Tested as you suggested, however didn't help. Please find attached log >>>> files for each firmware type. >>>> >>>> While executing following commands in sequence, captured dmesg. I hope >>>> those logs will help. If not please let me know. >>> >>> Thanks! >>> >>> Apparently I've missed from your original email the fact that you're >>> trying to inject packets. This isn't supported in ath10k. >> >> IMHO we should somehow warn the user or prevent that happening. Is there >> a way to do that? > > We could add an extra condition in ath10k_tx() to drop/free packets > immediately and warn if an injection attempt is made. Yeah, that would be really good to have. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k