From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from wolverine02.qualcomm.com ([199.106.114.251]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1WQuzw-0004ae-No for ath10k@lists.infradead.org; Fri, 21 Mar 2014 08:40:17 +0000 From: Kalle Valo Subject: Re: Failure to allocate large memory blocks upon firmware crash References: Date: Fri, 21 Mar 2014 10:39:48 +0200 In-Reply-To: (Avery Pennarun's message of "Wed, 19 Mar 2014 22:42:06 -0400") Message-ID: <87y504aqsr.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: Avery Pennarun Cc: ath10k Hi Avery, replying in smaller parts, easier to discuss that way. Avery Pennarun writes: > We are still getting firmware crashes occasionally, but I haven't > narrowed down the cause nor tried the very latest driver, so I won't > bother you with those just yet. Even if you are not using the latest and greatest ath10k I think you should still post the firmware crashes. Then we can try to analyse what's causing them. What I'm wondering is that why you seem to have firmware crashes so often. For example, I'm not seeing anything like that on our MIPS based AP135 platform. Maybe there are more memory barrier issues like you reported earlier? What kind of platform are you using? Does it have any special characteristics related to cache coherency, PCI access or similar? -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k