-
Notifications
You must be signed in to change notification settings - Fork 60
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
error in ubuntu 22.04 #35
Comments
thanks for the report.can you try "bpftune -ds" (should provide more debug info)? can you also confirm you're using latest "main" branch (there were some bugs impacting behaviour on ubuntu that are hopefully fixed now)? can you also provide info on which kernel you're using (uname -r) - i've been testing on an ubuntu 22.04 image using a 5.15 kernel. |
✘ cappelikan@cappelikan-775i945gz ~ sudo bpftune -ds |
✘ cappelikan@cappelikan-775i945gz ~ kinfo kde neon 5.27.6 based on ubuntu 22.04 lts |
thanks for the additional info! the problem is bpftune: libbpf: Unsupported BTF_KIND:19 The reason for this is the toolchain (libbpf+bpftool) used to build bpftune doesn't know about BTF_KIND_ENUM64 which is in the kernel BPF Type Format information (BTF) that is embedded when the kernel was built; the toolchain used to build the kernel BTF (pahole+libbpf) is newer than the toolchain used to build bpftune. To get libbpf enum64 support you would need a libbpf version 1.0.0 or later. Not sure if that's packaged for ubuntu yet; alternatively you could try building libbpf from source from github.com/libbpf/libbpf. The real issue here is that Ubuntu shouldn't build BTF for a 5.15 kernel with such new tools, or if they do they should omit the problematic BTF information. |
trying to solve this upstream so future BTF generation will not trip up like this; see https://lore.kernel.org/bpf/20230720201443.224040-1-alan.maguire@oracle.com/ |
from the bpftune side #54 merged a "no BTF" mode of operation which we should fall back to when BTF is missing or invalid (from bpftune's perspective). it's not ideal (because we don't get the automatic fixing of kernel data structure offsets so may be reading bad data), but it's the best we can do under the circumstances. |
now that we have "no BTF" mode of operation, closing this issue. we still have issue 37 open which covers the same area, so we can track any further problems there if needed. |
$ sudo service bpftune start
Warning: The unit file, source configuration file or drop-ins of bpftune.service changed on disk. Run 'systemctl daemon-reload' to reload units.
$ systemctl daemon-reload
$ sudo service bpftune start
$ sudo bpftune -s
bpftune: bpftune works in legacy mode
bpftune: bpftune supports per-netns policy (via netns cookie)
bpftune: could not load skeleton: No such process
bpftune: error initializing '/usr/lib64/bpftune//tcp_cong_tuner.so: No such process
bpftune: could not load skeleton: No such process
bpftune: error initializing '/usr/lib64/bpftune//tcp_buffer_tuner.so: No such process
bpftune: could not load skeleton: No such process
bpftune: error initializing '/usr/lib64/bpftune//route_table_tuner.so: No such process
bpftune: could not load skeleton: No such process
bpftune: error initializing '/usr/lib64/bpftune//net_buffer_tuner.so: No such process
bpftune: could not load skeleton: No such process
bpftune: error initializing '/usr/lib64/bpftune//netns_tuner.so: No such process
bpftune: could not load skeleton: No such process
bpftune: error initializing '/usr/lib64/bpftune//neigh_table_tuner.so: No such process
bpftune: could not load skeleton: No such process
bpftune: error initializing '/usr/lib64/bpftune//sysctl_tuner.so: No such process
bpftune: no ringbuf events to watch, exiting.
bpftune: could not initialize tuners in '/usr/lib64/bpftune/'
The text was updated successfully, but these errors were encountered: