Re: ath10k driver crashes whenever firmware crashes on ARM SoC

From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Adrian Chadd <adrian@freebsd.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	Avery Pennarun <apenwarr@gmail.com>
Subject: Re: ath10k driver crashes whenever firmware crashes on ARM SoC
Date: Wed, 12 Mar 2014 10:22:38 +0200	[thread overview]
Message-ID: <87pplrg71t.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <531F5D6F.6060801@candelatech.com> (Ben Greear's message of "Tue,  11 Mar 2014 12:01:03 -0700")

Ben Greear <greearb@candelatech.com> writes:

> On 03/11/2014 12:33 AM, Kalle Valo wrote:
> oes this ring a bell for anyone?  I think I can also export the
>>> traces as csv in case someone wants to look at them.
>> 
>> I showed your analysis to an HW engineer and the response I got was
>> "don't do that" (= don't use the cold reset).
>
> Earlier (1/22/14), you said a cold reset problem in CUS223 was due primarily to
> a bad piece of hardware (or bad design, or something) in the CUS223.
>
> I guess the problem must extend to other NICs as well, and
> maybe other reasons for causing the hangs?

I don't know the details, but I understood this only happens on CUS223.
If someone has seen these cold reset problems on other boards, like
XB140, I would be very keen to hear about it.

> Anything we can do to help debug the problem with warm resets
> failing to work properly in some cases?

Thanks, but not right now there isn't anything. Once I have new ideas
for the warm reset problems, I'll post them here. Testing those would be
very useful.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k