Bug 2022470
Summary: | Cannot find symbol for section 11: .text.unlikely. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Veronika Kabatova <vkabatov> |
Component: | gcc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 35 | CC: | aoliva, dmalcolm, fweimer, jakub, jwakely, law, mhofmann, mpolacek, msebor, nickc, sipoyare |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-12-13 15:50:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Veronika Kabatova
2021-11-11 17:57:16 UTC
Hi Veronika, > 00:02:53 Cannot find symbol for section 11: .text.unlikely. > 00:02:53 kernel/kexec_file.o: failed This message comes from the recordmcount tool, which is part of the kernel sources: linux/scripts/recordmcount.[ch] It appears to be triggered when a compiler update causes code to be rearranged. The problem has been reported before in various forums, but in particular I found this reference: https://lore.kernel.org/lkml/20201204165742.3815221-2-arnd@kernel.org/ The point of which to me at least is that this is a kernel issue rather than a compiler issue. Ie there must be some weak symbols in kexec_file.o file which need to be moved elsewhere. Does this make sense ? Cheers Nick (In reply to Nick Clifton from comment #1) > Hi Veronika, > > > 00:02:53 Cannot find symbol for section 11: .text.unlikely. > > 00:02:53 kernel/kexec_file.o: failed > > This message comes from the recordmcount tool, which is part of the kernel > sources: > > linux/scripts/recordmcount.[ch] > > It appears to be triggered when a compiler update causes code to be > rearranged. > The problem has been reported before in various forums, but in particular I > found this reference: > > https://lore.kernel.org/lkml/20201204165742.3815221-2-arnd@kernel.org/ > > The point of which to me at least is that this is a kernel issue rather than > a compiler issue. Ie there must be some weak symbols in kexec_file.o file > which need to be moved elsewhere. Does this make sense ? > Thanks for the analysis! I'll reach out to the devels to see if this is something that can be fixed or what the cause is. > Cheers > Nick This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |