From: Jon Hunter <jonathanh@nvidia.com>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
thierry.reding@gmail.com, vdumpa@nvidia.com, joro@8bytes.org,
will@kernel.org, robin.murphy@arm.com, baolu.lu@linux.intel.com,
jsnitsel@redhat.com, jroedel@suse.de,
linux-tegra@vger.kernel.org, iommu@lists.linux.dev,
regressions@lists.linux.dev
Subject: Re: [REGRESSION] Failed buffer allocation in Tegra fbdev
Date: Wed, 24 Jan 2024 10:36:16 +0000 [thread overview]
Message-ID: <a837d873-ee4c-460a-a157-6fbbda6dc09f@nvidia.com> (raw)
In-Reply-To: <xwvre6uqvakg7aqrnkxa3xrek4rkjoj36isiip2iphzanmmxch@gzqrwgqeljsi>
On 24/01/2024 10:30, Diogo Ivo wrote:
...
>>> Yes, this does fix the issue!
>>
>>
>> I am seeing the same error message on Tegra194 AGX Jetson. However, the
>> above does not seem to fix it. In this case it is slightly different as I am
>> not seeing the DRM allocation failure. In this case, it appears to be the
>> of_dma_configure_id() call from the host1x_memory_context_list_init()
>> function that is failing.
>>
>> Jon
>
> Just to clarify, when you mention the same error message which one are
> you referring to? In my case only the drm allocation is fixed with the
> above patch, and I am still getting the ENOENT.
OK, got it. In my case, I only see ...
ERR KERN host1x drm: iommu configuration for device failed with -ENOENT
Jon
--
nvpublic
next prev parent reply other threads:[~2024-01-24 10:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 14:33 [REGRESSION] Failed buffer allocation in Tegra fbdev diogo.ivo
2024-01-23 15:15 ` Jason Gunthorpe
2024-01-23 18:44 ` Diogo Ivo
2024-01-24 10:15 ` Jon Hunter
2024-01-24 10:30 ` Diogo Ivo
2024-01-24 10:36 ` Jon Hunter [this message]
2024-01-26 19:51 ` Jason Gunthorpe
2024-01-29 12:07 ` Diogo Ivo
2024-01-24 9:13 ` Diogo Ivo
2024-01-24 10:17 ` Jon Hunter
2024-01-24 11:46 ` Robin Murphy
2024-01-24 12:56 ` Diogo Ivo
2024-02-29 14:50 ` Jon Hunter
2024-02-29 16:46 ` Thierry Reding
2024-01-24 17:03 ` Jason Gunthorpe
2024-02-08 1:22 ` Robin Murphy
2024-02-08 2:31 ` Jason Gunthorpe
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=a837d873-ee4c-460a-a157-6fbbda6dc09f@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=diogo.ivo@tecnico.ulisboa.pt \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=jsnitsel@redhat.com \
--cc=linux-tegra@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=thierry.reding@gmail.com \
--cc=vdumpa@nvidia.com \
--cc=will@kernel.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