From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx2.sophos.com ([145.253.124.138]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1YYcpG-0006ug-1z for ath10k@lists.infradead.org; Thu, 19 Mar 2015 15:57:40 +0000 Message-ID: <550AF1D6.80907@sophos.com> Date: Thu, 19 Mar 2015 16:57:10 +0100 From: Fabian Wittenberg MIME-Version: 1.0 Subject: Re: ath10k + INTEL_IDLE aka. cstates == firmware crash References: <54EB264D.5040805@sophos.com> <54EB2ED5.8040104@sophos.com> <54EB3C30.60302@sophos.com> <8ab73bee-735c-4140-a050-e52fb2afd5b5@DE-WIE-EXCH3A.green.sophos> In-Reply-To: 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: Adrian Chadd Cc: Michal Kazior , "ath10k@lists.infradead.org" Yes, I guessed something like that but this should be a firmwarebug :-\ I'm quiet surprized that nowbody else has this problem!? There are so many configuration constellations that trigger this... Fabian Am 19.03.2015 um 16:44 schrieb Adrian Chadd: > It's possible that you're entering a sleep state, the whole socket + > dram controller is going to sleep, and the latency that the wakeup > causes is confusing the firmware and/or DMA engine. > > > > -adrian _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k