From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from wolverine01.qualcomm.com ([199.106.114.254]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1W8YFb-0001Gk-K5 for ath10k@lists.infradead.org; Wed, 29 Jan 2014 16:44:32 +0000 From: Kalle Valo Subject: Re: ath10k driver crashes whenever firmware crashes on ARM SoC References: <52E7F4F2.2030001@candelatech.com> Date: Wed, 29 Jan 2014 18:44:02 +0200 In-Reply-To: (Avery Pennarun's message of "Tue, 28 Jan 2014 13:34:59 -0500") Message-ID: <87wqhizqjx.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: Ben Greear , ath10k Avery Pennarun writes: > On Tue, Jan 28, 2014 at 1:20 PM, Ben Greear wrote: >> On 01/28/2014 09:18 AM, Avery Pennarun wrote: >>> When the ath10k firmware crashes on my device (let's not worry about >>> why the firmware crashes right now; one problem at a time), my host >>> CPU (ARMv7 based) can't recover. I get some variant of this error: >> >> I don't know about your pci bus problem, but I'm interested in knowing >> about firmware crashes (if you are at liberty to share the details). > > Well, since you asked... :) > > I'm trying to build an especially robust system here, so when I > noticed that the driver will bring the entire system crashing down > upon a firmware crash, I've actually gone out of my way to make more > firmware crashes. Do you know that we have simulate_fw_crash debugfs file just for testing this? Of course it's good to test various firmware crashing scenarious, but in some cases this debugfs file helps a lot. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k