From: Kalle Valo <kvalo@codeaurora.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: "open list\:DRM DRIVER FOR MSM ADRENO GPU"
<linux-arm-msm@vger.kernel.org>,
ath11k@lists.infradead.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: ath11k/mhi backtraces on shutdown with linux-next
Date: Thu, 07 Oct 2021 12:27:09 +0300 [thread overview]
Message-ID: <871r4xchhu.fsf@codeaurora.org> (raw)
In-Reply-To: <87y2hxvbu8.fsf@codeaurora.org> (Kalle Valo's message of "Wed, 16 Dec 2020 20:34:55 +0200")
Kalle Valo <kvalo@codeaurora.org> writes:
> Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:
>
>> On Sat, 12 Dec 2020 at 08:11, Kalle Valo <kvalo@codeaurora.org> wrote:
>>>
>>> Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:
>>>
>>> > Hello,
>>> >
>>> > I've noticed the following backtrace during shutdown stage when
>>> > rebooting RB5 board,
>>> > using linux-next/master:
>>> >
>>> > [ 31.060483] ath11k_pci 0000:01:00.0: shutdown
>>> > [ 31.067844] ------------[ cut here ]------------
>>> > [ 31.073111] WARNING: CPU: 4 PID: 101 at
>>> > drivers/iommu/io-pgtable-arm.c:583 __arm_lpae_unmap+0x39c/0x550
>>>
>>> Do you have CONFIG_DMA_API_DEBUG disabled? There is one commit fixing a
>>> DMA API debug warning but that should be in linux-next already:
>>>
>>> cd6181ff7e93 ath11k: dp_rx: fix monitor status dma unmap direction
>>
>> I have enabled CONFIG_DMA_API_DEBUG (and _SG too). Got no additional
>> traces during boot and the same trace during reboot.
>
> On x86 I see this during rmmod when iommu is enabled:
>
> [ +0.012066] DMAR: DRHD: handling fault status reg 2
> [ +0.000022] DMAR: [DMA Write] Request device [06:00.0] PASID ffffffff
> fault addr 0 [fault reason 05] PTE Write access is not set
> [ +0.014657] DMAR: DRHD: handling fault status reg 2
> [ +0.000017] DMAR: [DMA Write] Request device [06:00.0] PASID ffffffff
> fault addr 0 [fault reason 05] PTE Write access is not set
>
> Is that the similar issue you are seeing, but just the printouts are
> different due to different iommu implementation?
BTW, this patch should fix this:
https://patchwork.kernel.org/project/linux-wireless/patch/20210913180246.193388-5-jouni@codeaurora.org/
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-10-07 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 1:23 ath11k/mhi backtraces on shutdown with linux-next Dmitry Baryshkov
2020-12-12 5:11 ` Kalle Valo
2020-12-12 21:04 ` Dmitry Baryshkov
2020-12-16 18:34 ` Kalle Valo
2021-10-07 9:27 ` Kalle Valo [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=871r4xchhu.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).