From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: master-pending: ODEBUG: free active (active state 0) object type: timer_list hint: ath10k_htt_rx_ring_refill_retry+0x0/0x10 [ath10k_core]
Date: Mon, 22 Aug 2016 14:25:14 +0000 [thread overview]
Message-ID: <8760qsx4mv.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <daf51642-2979-5376-d3e4-8a5e22c5504c@candelatech.com> (Ben Greear's message of "Thu, 18 Aug 2016 08:18:59 -0700")
Ben Greear <greearb@candelatech.com> writes:
> On 08/18/2016 08:09 AM, Valo, Kalle wrote:
>> Hi,
>>
>> I was testing master-pending branch and saw these warnings when I was
>> reloading ath10k. I have seen this two times out of two tests so seems
>> to be easy to reproduce. I don't have time to investigate this more at
>> this time but I'll post this anyway.
>
> I'm not sure I am seeing the same issue, but this patch below helps
> keep me from crashing when firmware dies. I'm not sure the spinlock
> change matters, but the txq_unref fixes the crash....
This didn't apply for me but I see that you submitted them as proper
patches later. I'll test those when I start debugging this NAPI issue
more.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-08-22 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 15:09 master-pending: ODEBUG: free active (active state 0) object type: timer_list hint: ath10k_htt_rx_ring_refill_retry+0x0/0x10 [ath10k_core] Valo, Kalle
2016-08-18 15:18 ` Ben Greear
2016-08-22 14:25 ` Valo, Kalle [this message]
2016-08-18 15:20 ` Valo, Kalle
2016-08-19 11:51 ` Valo, Kalle
2016-08-19 12:14 ` Manoharan, Rajkumar
2016-08-22 14:22 ` Valo, Kalle
2016-08-24 15:39 ` Manoharan, Rajkumar
2016-08-26 17:43 ` Valo, Kalle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760qsx4mv.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.