-
Notifications
You must be signed in to change notification settings - Fork 119
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
Illegal instruction scrn_constructor () #255
Comments
I have tried on virtual machine, and another mini PC, I got same core dump above, now I started to think if it is something I did wrong, but I could not since the installation is straightforward to me, the steps I roughly take are
|
Most likely the CPU's being used are not supporting all of the features required by DPDK. DPDK needs a minimum set of CPU features to work and a VM may not support that feature or a Non-XEON processors. |
The scrn_constructor() routine is some pretty simple and should not require anything special in the CPU. If you are copy the binary from one machine to the other machine this could be the problem too. DPDK reads the features during build and builds the binary specific to the machine. I think DPDK can be built with a minimum set of features via command line, but I do not remember how that is done. |
thanks for the reply, it sounds like I did not do something silly :). I did not copy the binary, I build the binary on each test machine, a mini PC, a VM, a real dell power edge r730, they all got same scrn_constructor dump. I have one dell power edge r210 server working |
dpdk
my mini pc has no avx
|
@KeithWiles someone from https://stackoverflow.com/questions/75098061/wrong-detection-of-cpu-instruction-during-dpdk-build mentioned to build dpdk app with |
I rely on DPDK doing the correct thing here with CPU flags. I do not remember using any thing special in Pktgen code to need using the rte_cpu_is_supported() function. It could be the compilers are different between the machines, but just shooting in the dark here. Would need to debug the problem on the machine and I do not have access to a machine, sorry not much help here. I would prefer not to use external machines it kind of opens me up to some legal issues IMO. |
You can try putting printf() in the routine and see where it fails. Remember add a flush(stdout) to make sure the text gets printed. Using something like this following the code path. printf("%s:%d Entry\n", func, LINE); flush(stdout); printf("%s:%d Here 1\n", func, LINE); flush(stdout); printf("%s:%d Here 2\n", func, LINE); flush(stdout); printf("%s:%d Exit\n", func, LINE); flush(stdout); |
the code path in
|
I was thinking the scrn_constructor(), but in the above locations is fine too. |
Hi
I have two dell servers running same Ubuntu 22.04 version but with different dell model. pktgen runs fine on one dell server, same steps to install pktgen on another Dell server, pktgen core dumped. let me know what else information you need, thanks!
dpdk NIC:
huge page:
dpdk-hugepages.py -p 2M --setup 2G
run pktgen
The text was updated successfully, but these errors were encountered: