ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "Manoharan, Rajkumar" <rmanohar@qti.qualcomm.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: Fri, 26 Aug 2016 17:43:24 +0000	[thread overview]
Message-ID: <87k2f3juis.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1472053193355.82012@qti.qualcomm.com> (Rajkumar Manoharan's message of "Wed, 24 Aug 2016 15:39:53 +0000")

"Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com> writes:

>>> If possible, could you please try below change?
>>>
>>> diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
>>> index 33380fba5948..29fc9052e51a 100644
>>> --- a/drivers/net/wireless/ath/ath10k/pci.c
>>> +++ b/drivers/net/wireless/ath/ath10k/pci.c
>>> @@ -1759,6 +1759,7 @@ void ath10k_pci_ce_deinit(struct ath10k *ar)
>>>
>>>  void ath10k_pci_flush(struct ath10k *ar)
>>>  {
>>> +       napi_synchronize(&ar->napi);
>>>         ath10k_pci_rx_retry_sync(ar);
>>>         ath10k_pci_buffer_cleanup(ar);
>>>  }
>>
>> Sorry, didn't help:
>>
> It seems napi synchronization alone is not sufficient. NAPI should be disabled. Need your help again. ;)
> With below change WARNING & KASAN BUG is gone. Could you please help to verify below change?
>
> diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
> index 6e21fa1478ea..04ff45deb173 100644
> --- a/drivers/net/wireless/ath/ath10k/pci.c
> +++ b/drivers/net/wireless/ath/ath10k/pci.c
> @@ -1775,6 +1775,8 @@ static void ath10k_pci_hif_stop(struct ath10k *ar)
>          */
>         ath10k_pci_safe_chip_reset(ar);
>  
> +       napi_synchronize(&ar->napi);
> +       napi_disable(&ar->napi);
>         ath10k_pci_irq_disable(ar);
>         ath10k_pci_irq_sync(ar);
>         ath10k_pci_flush(ar);
> @@ -2531,6 +2533,7 @@ static int ath10k_pci_hif_power_up(struct ath10k *ar)
>                 ath10k_err(ar, "could not wake up target CPU: %d\n", ret);
>                 goto err_ce;
>         }
> +       napi_enable(&ar->napi);
>  
>         return 0;
>  
> @@ -2878,7 +2881,6 @@ void ath10k_pci_init_napi(struct ath10k *ar)
>  {
>         netif_napi_add(&ar->napi_dev, &ar->napi, ath10k_pci_napi_poll,
>                        ATH10K_NAPI_BUDGET);
> -       napi_enable(&ar->napi);
>  }

The patch was corrupted but I did the same changes manually. And now I
can't get it to crash anymore, earlier that was really easy.

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

      reply	other threads:[~2016-08-26 17:43 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
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 [this message]

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=87k2f3juis.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=rmanohar@qti.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox