-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ld.lld: error: drivers/gpu/drm/amd/amdgpu/amdgpu.o:(.debug_info+0x7d117f5): unknown relocation (33554442) against symbol #2034
Comments
With disabling both modules: $ scripts/config -d DRM_AMDGPU -d DRM_NOUVEAU I was able to build and boot into my Debian/unstable AMD64 system: root# cat /proc/version |
I tried with and without revert of: $ git revert f1feed6 |
Can you look at this, please? |
I am NOT able to assign labels. |
I think you should be able to now? We did a massive role update a few months ago, so I have given you the triage role for this repo now. As for both this issue and #2035, I cannot reproduce this on my system or a Debian container with
Is this fully reproducible for you? Can you try to |
Thanks for taking care and providing step-by-step instructions (sorry German output):
INFO: Used vanilla Linux v6.9.7 (no modifications) and pahole v1.27-7-g693522ee3a94 UPDATE: Booting on bare metal OK
|
Can you please test with my make line (resulting in BROKEN build)?
|
Still works for me (
|
@nathanchance For my first build I reverted this commit (the BROKEN build):
In the upstream report you will find this information - here in this issue I forgot to mention it. |
Can you try removing |
Did you get a build-error with When - in the build-process - shall I remove |
No, either on the first revert or a rebuild using the cache. If you want to run with that change reverted, you are free to do so, but since it was removed due to known bugs, supporting it will be done on a best effort basis.
Do it before the build so that it is created from scratch from that build. |
Is there a complete reproduce that doesn't require knowledge about the kernel build system ? :) |
My initial motivation was to see the impact of...
...to the build-time on my Debian/unstable AMD64 system. That commit was applied to Linux v6.9 series and others. As reported in #2021 (comment) - for me it has NO IMPACT.
The big advantage is the reduction by 6GB in disc-usage - not using thinlto-caching. For me carrying the revert is like riding a DEAD horse.
Before a build, I am always doing a It's up to you if you want to test the BROKEN scenario. I will re-test with upcoming Linux v6.9.8 - I will use VANILLA stable version - no modifications. |
If you do a |
I am very thankful for your precious life-time and feedback. INFO: I have deferred updates to my Debian/unstable AMD64 system to test this all. NOTE: A build takes here approx. 18000 secs = 300 mins = 5 hrs (disabled amdgpu + nouveau kernel-modules). With Linux version 6.9.8, I'll be happy to provide further feedback. With Linux version 6.10-rc7 I'll switch to 6.10 series soon. You can wait for my feedback or CLOSE this as wont-fix or not-reproducible. |
Released 35 mins ago. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=v6.9.8 |
@nathanchance Normally, I would expect to work - but I had IIRC no success:
UPDATE: Maybe it should be |
FWIW, your Otherwise, if you have all your previous build artifacts around, your command should work to my understanding. If you do not have |
Looks good:
|
Looks like Debian does NOT pass
|
With Clang-ThinLTO and CONFIG_DEBUG_INFO_BTF=y and CONFIG_DEBUG_INFO_BTF_MODULES=y and CONFIG_DEBUG_INFO_DWARF5=y amdgpu kernel-module is BROKEN with Linux v6.9.7:
SLIM LLLVM toolchain version 18.1.8 was used from kernel.org.
Reported upstream (it does not look like a BTF/pahole issue);
Link: https://lore.kernel.org/all/CA+icZUU71k9kh3GGc8w=F4rdJeBc3LOPH-gNXrjTTUicnufe5g@mail.gmail.com/
BROKEN linux-config is attached.
config-6.9.7-1-amd64-clang18-kcfi.txt
The text was updated successfully, but these errors were encountered: