-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
libbpf: Error loading BTF: Invalid argument(22) #63
Comments
|
So with libbfp0 from ubuntu 22.10 it doesn't do this? |
Unfortunetly no - and in version libbpf 0.8 there are more errors like:
Maybe something needs to be recompiled with libbpf0-dev 0.8 version? |
Gotcha. Since the libbpf library is under xdp-cpumap-tc it may be necessary to make a change in xdp-cpumap-tc to avoid these errors with more modern libbpf versions. |
You are right so I did: libbpf/libbpf#580 |
Look at libbpf github header: |
@rchac maybe You should add libbfp1 as a dependancy in wiki instruction (newest LTS of ubuntu uses obsolette 0.5) ? |
Tried removing libbpf0 but it breaks the OS (many things depend on it apparently). I thought xdp-cpumap-tc just loaded the libbpf version it includes in it's directory. But when I tried that, I couldn't get xdp redirect to actually work. How did you manage to get it working? |
I do very dirty force upgrade using package libbpg1 from other ubuntu to test that and remove libbpf0. |
I was able to figure it out. Installing 22.04 from scratch, and following the Wiki step-by-step works. I think it may have been that I installed libbpf from a bad package at some point a while ago on this particular machine. I use a mellanox card, and at one step during the ubuntu install it asks whether to install drivers for Mellanox/Intel. I chose yes this time. That may have helped. It should not be necessary to remove libbpf0. |
This warning no more occurs with |
The solution found on stackoverflow is:
xdp-project/xdp-tutorial#38 (comment)
and
Second solution:
Maybe libbpf should be also compiled from source? There are many changes from 0.5 to 0.8 (not only this warning).
The text was updated successfully, but these errors were encountered: