From: diogo.ivo@tecnico.ulisboa.pt
To: thierry.reding@gmail.com, vdumpa@nvidia.com, joro@8bytes.org,
will@kernel.org, robin.murphy@arm.com, jonathanh@nvidia.com,
jgg@ziepe.ca, baolu.lu@linux.intel.com, jsnitsel@redhat.com,
jroedel@suse.de, linux-tegra@vger.kernel.org,
iommu@lists.linux.dev, regressions@lists.linux.dev
Cc: diogo.ivo@tecnico.ulisboa.pt
Subject: [REGRESSION] Failed buffer allocation in Tegra fbdev
Date: Tue, 23 Jan 2024 14:33:15 +0000 [thread overview]
Message-ID: <bbmhcoghrprmbdibnjum6lefix2eoquxrde7wyqeulm4xabmlm@b6jy32saugqh> (raw)
Commit c8cc2655cc6c in the recent IOMMU changes breaks Tegra fbdev
at least on the Pixel C with the following error message reporting
a failed buffer allocation:
[ 1.857660] drm drm: failed to allocate buffer of size 18432000
This error message is printed from tegra_bo_alloc() which is called by
tegra_bo_create() in tegra_fbdev_probe(), which may indicate that other
allocations would fail as well, not just the framebuffer.
This may be connected with an error in of_iommu_configure() that
became visible after commit 6ff6e184f1f4d:
[ 1.200004] host1x drm: iommu configuration for device failed with -ENOENT
Best regards,
Diogo
#regzbot introduced: c8cc2655cc6c
next reply other threads:[~2024-01-23 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 14:33 diogo.ivo [this message]
2024-01-23 15:15 ` [REGRESSION] Failed buffer allocation in Tegra fbdev 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
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=bbmhcoghrprmbdibnjum6lefix2eoquxrde7wyqeulm4xabmlm@b6jy32saugqh \
--to=diogo.ivo@tecnico.ulisboa.pt \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=jonathanh@nvidia.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).