1. Please describe the problem: As described in bug 2059838, currently gcc doesn't add the .text.unlikely section symbol for ppc64le. And scritps/recordmcount would quit with the error "Cannot find symbol for section 11: .text.unlikely.". Thus kernel building would fail. However the perl verion scritps/recordmcount.pl can deal with this situation because it uses a global variable as a reference when building _mcount_loc, $ readelf -a kernel/kexec_file.o ... Relocation section '.rela__mcount_loc' at offset 0x56f8 contains 18 entries: Offset Info Type Sym. Value Sym. Name + Addend 000000000000 007100000026 R_PPC64_ADDR64 0000000000000830 kexec_image_probe[...] - 824 000000000008 007100000026 R_PPC64_ADDR64 0000000000000830 kexec_image_probe[...] - 614 000000000010 007100000026 R_PPC64_ADDR64 0000000000000830 kexec_image_probe[...] - 404 000000000018 007100000026 R_PPC64_ADDR64 0000000000000830 kexec_image_probe[...] + c 000000000020 007100000026 R_PPC64_ADDR64 0000000000000830 kexec_image_probe[...] + dc 000000000028 007100000026 R_PPC64_ADDR64 0000000000000830 kexec_image_probe[...] + 1ac 2. What is the Version-Release number of the kernel: 5.16.11-200.fc35.ppc64le 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: a.. use a kernel .config file from https://gitlab.com/api/v4/projects/18194050/jobs/2142072138/artifacts/artifacts/kernel-mainline.kernel.org-ppc64le-7e57714cd0ad2d5bb90e50b5096a0e671dec1ef3.config b. make 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: 6. Are you running any modules that not shipped with directly Fedora's kernel?: 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
Hi Jerome, You may want to take a look at this bug as my colleges told me you are the maintainer of ftrace.
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.