From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: amd-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, alexander.deucher@amd.com,
george.zhang@amd.com, bhawanpreet.lakha@amd.com,
LKML <linux-kernel@vger.kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
christian.koenig@amd.com, harry.wentland@amd.com,
sunpeng.li@amd.com, broonie@kernel.org,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: [REGRESSION] drm/amd/display: amdgpu_dm_plane_test.ko fails to build due to modpost "too long symbol"
Date: Wed, 8 Jul 2026 10:35:14 +0530 [thread overview]
Message-ID: <fde3656e-9e22-4e4c-937f-7e8cb918da6b@linux.ibm.com> (raw)
Greetings!!!
linux-next is failing to build for me with:
ERROR: modpost: too long symbol
"amdgpu_dm_plane_fill_gfx9_plane_attributes_from_modifiers"
[drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/tests/amdgpu_dm_plane_test.ko]
make[2]: *** [scripts/Makefile.modpost:147: Module.symvers] Error 1
make[1]: *** [Makefile:2165: modpost] Error 2
make: *** [Makefile:248: __sub-make] Error 2
The failure occurs during modpost while building:
drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_plane_test.ko
This appears to be a regression in the AMD display KUnit test code.
Could someone please take a look?
If you happen to fix this, please add below tag.
Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Regards,
Venkat.
next reply other threads:[~2026-07-08 5:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 5:05 Venkat Rao Bagalkote [this message]
2026-07-09 18:23 ` [REGRESSION] drm/amd/display: amdgpu_dm_plane_test.ko fails to build due to modpost "too long symbol" Randy Dunlap
2026-07-10 5:15 ` Venkat Rao Bagalkote
2026-07-10 8:01 ` Venkat Rao Bagalkote
2026-07-10 8:52 ` Venkat Rao Bagalkote
2026-07-10 9:43 ` Christophe Leroy (CS GROUP)
2026-07-10 20:03 ` Deucher, Alexander
2026-07-10 20:43 ` Alex Hung
2026-07-11 3:43 ` Venkat
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=fde3656e-9e22-4e4c-937f-7e8cb918da6b@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bhawanpreet.lakha@amd.com \
--cc=broonie@kernel.org \
--cc=chleroy@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=george.zhang@amd.com \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=sunpeng.li@amd.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