Return-path: Received: from wolverine02.qualcomm.com ([199.106.114.251]:29437 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932617AbbELMT0 (ORCPT ); Tue, 12 May 2015 08:19:26 -0400 From: Kalle Valo To: Michal Kazior CC: s prasad , linux-wireless , "ath10k@lists.infradead.org" Subject: Re: Ath10 firmware crashing in Monitor mode(Sniffer mode) References: Date: Tue, 12 May 2015 15:19:17 +0300 In-Reply-To: (Michal Kazior's message of "Tue, 12 May 2015 07:03:42 +0200") Message-ID: <87iobygf96.fsf@kamboji.qca.qualcomm.com> (sfid-20150512_141944_689788_826AA870) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: linux-wireless-owner@vger.kernel.org List-ID: 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? -- Kalle Valo