Bug ID 1229450
Summary libbpf: failed to find '.BTF' ELF section in vmlinux
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee kernel-bugs@opensuse.org
Reporter jslaby@suse.com
QA Contact qa-bugs@suse.de
Target Milestone ---
Found By ---
Blocker ---

Created attachment 876820 [details]
Devel:Kernel:master/kernel-source:kernel-vanilla/LEGACYX86/i586 build log

The kernel builds result in random build failures while creating BTF.

For example
https://build.opensuse.org/package/live_build_log/Kernel:vanilla/kernel-source-vanilla:kernel-vanilla/ARM/armv7l:
> libbpf: failed to find '.BTF' ELF section in vmlinux
> FAILED: load BTF from vmlinux: No data available
> make[2]: *** [../scripts/Makefile.vmlinux:34: vmlinux] Error 255
> make[2]: *** Deleting file 'vmlinux'
> make[1]: *** [/home/abuild/rpmbuild/BUILD/kernel-vanilla-6.11~rc3.338.gc3f2d783a459/linux-6.11-rc3-338-gc3f2d783a459/Makefile:1158: vmlinux] Error 2
> make: *** [../Makefile:224: __sub-make] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.olf5Nu (%build)

arm seems to fail reliably.

But for example in
ibs://Devel:Kernel:master/kernel-source:kernel-vanilla/LEGACYX86/i586, it looks
like it is sort of random. kernel-debug and kernel-vanilla fails for i586, but
-default and -pae are built currently. See the job history for kernel-vanilla
in there (the failed boot log is attached):
> time                 package                       reason           code       build time      worker 
> 2024-07-15 07:41:48  kernel-source:kernel-vanilla  source change    succeeded        47m 53s   h01-ch5a:3      
> 2024-07-15 23:56:48  kernel-source:kernel-vanilla  source change    succeeded        47m 57s   h01-ch5b:5      
> 2024-07-18 11:12:40  kernel-source:kernel-vanilla  source change    succeeded        48m 46s   h01-ch5b:2      
> 2024-07-26 20:01:29  kernel-source:kernel-vanilla  source change    succeeded        52m 40s   h01-ch4b:2      
> 2024-07-29 09:07:35  kernel-source:kernel-vanilla  source change    succeeded        52m 53s   h01-ch4a:6      
> 2024-08-03 11:38:55  kernel-source:kernel-vanilla  source change    failed           25m 16s   h01-ch4b:8      
> 2024-08-04 23:48:15  kernel-source:kernel-vanilla  source change    failed           25m 14s   h01-ch4b:7      
> 2024-08-06 16:37:35  kernel-source:kernel-vanilla  source change    succeeded        53m 25s   h01-ch4b:4      
> 2024-08-09 19:44:44  kernel-source:kernel-vanilla  source change    failed           26m  4s   h01-ch5a:2      
> 2024-08-11 22:48:56  kernel-source:kernel-vanilla  source change    failed            0m 38s   h01-ch4b:6      
> 2024-08-12 16:44:52  kernel-source:kernel-vanilla  source change    succeeded        54m  0s   h01-ch5b:5      
> 2024-08-15 21:49:11  kernel-source:kernel-vanilla  source change    failed           25m 25s   h01-ch4b:1      
> 2024-08-19 01:53:01  kernel-source:kernel-vanilla  source change    succeeded        50m  9s   h01-ch4a:5      
> 2024-08-19 11:33:50  kernel-source:kernel-vanilla  source change    succeeded        55m  9s   h01-ch5b:1      
> 2024-08-19 17:23:59  kernel-source:kernel-vanilla  source change    failed           25m 16s   h01-ch5a:3


You are receiving this mail because: