From: Shuah Khan <skhan@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Alexander Deucher <Alexander.Deucher@amd.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
amd-gfx@lists.freedesktop.org,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Linux 6.18 amdgpu build error
Date: Wed, 3 Dec 2025 15:16:24 -0700 [thread overview]
Message-ID: <9d520a1d-0b8d-4d30-b29f-230fc0f92b8a@linuxfoundation.org> (raw)
In-Reply-To: <ec77d11a-7613-4b75-8c9e-f2bba1595f0f@roeck-us.net>
On 12/2/25 14:23, Guenter Roeck wrote:
> On 12/2/25 13:01, Shuah Khan wrote:
>> On 12/1/25 19:31, Guenter Roeck wrote:
>>> On Mon, Dec 01, 2025 at 03:17:49PM -0700, Shuah Khan wrote:
>>>> Hi Alex,
>>>>
>>>> I am seeing the following make error on Linux 6.18.
>>>> I started seeing build failures since rc7 and rc6
>>>> build was just fine on the same config file.
>>>>
>>>> LD [M] drivers/gpu/drm/amd/amdgpu/amdgpu.o
>>>> drivers/gpu/drm/amd/amdgpu/amdgpu.o: error: objtool: elf_init_reloc: .rela.orc_unwind_ip: reloc 39935 already initialized!
>>>> make[6]: *** [scripts/Makefile.build:503: drivers/gpu/drm/amd/amdgpu/amdgpu.o] Error 255
>>>> make[6]: *** Deleting file 'drivers/gpu/drm/amd/amdgpu/amdgpu.o'
>>>> make[5]: *** [scripts/Makefile.build:556: drivers/gpu/drm/amd/amdgpu] Error 2
>>>> make[4]: *** [scripts/Makefile.build:556: drivers/gpu/drm] Error 2
>>>> make[3]: *** [scripts/Makefile.build:556: drivers/gpu] Error 2
>>>> make[2]: *** [scripts/Makefile.build:556: drivers] Error 2
>>>> make[1]: *** [/linux/linux_6.18/Makefile:2010: .] Error 2
>>>> make: *** [Makefile:248: __sub-make] Error 2
>>>>
>>>> I tried "make clean" and "make distclean" just in case, still see
>>>> the same error.
>>>>
>>>
>>> My test system does not report any problems. What is the configuration
>>> and compiler ?
>>>
>>
>> My one test system didn't report any problems. The other one did.
>> I am using gcc and the config is the same as the one used to build
>> 6.18-rc6 with no issues.
>>
>> I will keep digging to find what's wrong on my system.
>>
>> gcc version 14.2.0 (Debian 14.2.0-19)
>>
>
> Interesting. That reminds me ... I used to have that kind of machine specific
> problems when building with CONFIG_RANDSTRUCT enabled. I worked around it
> by using gcc builds with plugin support disabled. In my case, there was
> nothing wrong with the system, just that each system has a slightly different
> hardware configuration which somehow influenced structure randomization, even
> across "make clean/distclean".
>
CONFIG_RANDSTRUCT is disabled and so are the GCC_PLUGINS in my config.
I am also seeing issues with cloning kernel.org repos on my system after
a recent update:
remote: Enumerating objects: 11177736, done.
remote: Counting objects: 100% (1231/1231), done.
remote: Compressing objects: 100% (624/624), done.
remote: Total 11177736 (delta 855), reused 781 (delta 606), pack-reused 11176505 (from 1)
Receiving objects: 100% (11177736/11177736), 3.01 GiB | 7.10 MiB/s, done.
Resolving deltas: 100% (9198323/9198323), done.
fatal: did not receive expected object 0002003e951b5057c16de5a39140abcbf6e44e50
fatal: fetch-pack: invalid index-pack output
Happy start to the end of the year :(
thanks,
-- Shuah
next prev parent reply other threads:[~2025-12-03 22:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 22:17 Linux 6.18 amdgpu build error Shuah Khan
2025-12-01 22:29 ` Deucher, Alexander
2025-12-02 2:31 ` Guenter Roeck
2025-12-02 21:01 ` Shuah Khan
2025-12-02 21:23 ` Guenter Roeck
2025-12-03 22:16 ` Shuah Khan [this message]
2025-12-03 23:58 ` Bagas Sanjaya
2025-12-04 1:06 ` Guenter Roeck
2025-12-04 2:34 ` Shuah Khan
2025-12-04 6:05 ` David Hildenbrand (Red Hat)
2025-12-04 17:40 ` Shuah Khan
2025-12-04 19:36 ` Linus Torvalds
2025-12-04 19:45 ` David Hildenbrand (Red Hat)
2025-12-04 23:20 ` Shuah Khan
2025-12-04 23:23 ` Linus Torvalds
2025-12-04 23:28 ` Shuah Khan
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=9d520a1d-0b8d-4d30-b29f-230fc0f92b8a@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Alexander.Deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=torvalds@linux-foundation.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