From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Peter Oh <poh@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
Peter Oh <poh@qca.qualcomm.com>
Subject: Re: [PATCH] ath10k: use pre-allocated DMA buffer in Tx
Date: Thu, 8 Oct 2015 20:41:48 +0300 [thread overview]
Message-ID: <87fv1ltfz7.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5616A511.5060705@codeaurora.org> (Peter Oh's message of "Thu, 8 Oct 2015 10:17:05 -0700")
Peter Oh <poh@codeaurora.org> writes:
> Does it happen after you applied copy engine patchset or even without
> the patchset? I saw ath10k_pci_htt_tx_cb in backtrace which is not
> merged to master branch yet. If it only happens after the patchset,
> I'll apply them and look into it if any possibilities are there.
Good point. I thought I was able to reproduce the bug with a clean
master branch, but I now checked the logs and all three cases of this
warning had ath10k_pci_htt_tx_cb in the stack trace. So I must have
accidentally tested with a temporary branch where the pending branch was
merged with master branch.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Peter Oh <poh@codeaurora.org>
Cc: Peter Oh <poh@qca.qualcomm.com>, <linux-wireless@vger.kernel.org>,
<ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: use pre-allocated DMA buffer in Tx
Date: Thu, 8 Oct 2015 20:41:48 +0300 [thread overview]
Message-ID: <87fv1ltfz7.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5616A511.5060705@codeaurora.org> (Peter Oh's message of "Thu, 8 Oct 2015 10:17:05 -0700")
Peter Oh <poh@codeaurora.org> writes:
> Does it happen after you applied copy engine patchset or even without
> the patchset? I saw ath10k_pci_htt_tx_cb in backtrace which is not
> merged to master branch yet. If it only happens after the patchset,
> I'll apply them and look into it if any possibilities are there.
Good point. I thought I was able to reproduce the bug with a clean
master branch, but I now checked the logs and all three cases of this
warning had ath10k_pci_htt_tx_cb in the stack trace. So I must have
accidentally tested with a temporary branch where the pending branch was
merged with master branch.
--
Kalle Valo
next prev parent reply other threads:[~2015-10-08 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 17:54 [PATCH] ath10k: use pre-allocated DMA buffer in Tx Peter Oh
2015-09-24 17:54 ` Peter Oh
2015-10-06 12:05 ` Kalle Valo
2015-10-06 12:05 ` Kalle Valo
2015-10-08 11:49 ` Kalle Valo
2015-10-08 11:49 ` Kalle Valo
2015-10-08 17:17 ` Peter Oh
2015-10-08 17:17 ` Peter Oh
2015-10-08 17:41 ` Kalle Valo [this message]
2015-10-08 17:41 ` Kalle Valo
2015-10-08 17:44 ` Peter Oh
2015-10-08 17:44 ` Peter Oh
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=87fv1ltfz7.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=poh@codeaurora.org \
--cc=poh@qca.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 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.