RSS Feed
Knowledgebase : ExaNIC X10/X40
modprobe: ERROR: could not insert 'exanic': Required key not available This happened on a new system of ours. The fix was to change a BIOS setting from Windows to "Other OS". This then changed the "Secure boot" setup of the host and the module could be ...
Received packets : Ignored vs Error vs Dropped Looking at a sample from exanic-config: _RX packets: 1514936895 ignored: 20578657 error: 145683 dropped: 0_ REGARDING EXANIC-CONFIG: The "RX Packets" counter refers to the number of packets received to NI...
This problem occurs due to Linux memory fragmentation. The function needs to allocate contiguous memory to operate. If a machine is up for a long time (especially if it undergoes heavy memory churn), memory can become fragmented and congested which limits...
We use sockperf for testing because it is open-source, well understood and has similar properties to real applications. For this example we use the ExaNIC X10. The ExaNIC X4 is our first generation NIC so it will be a bit slower than the X10 ( about 170...
The "Rollover timer fired at an unexpected time" message is a warning message from the ExaNIC driver code that extends the 32 bit time provided by the ExaNIC to 64 bits, which works by setting a timer to fire when the time counter is expected to wrap arou...
This error message "modprobe: FATAL: Module exanic not found" can be caused by two issues, when using the exanic driver delivered by dkms:- * If the module is built for the running kernel and the system cannot find it to load into the system, in which ...
We aim to support any spec-compliant SFP. We use a large number of Finisar, 10GTek, FiberStore and Exablaze SFPs in our lab, and we've got several customers using Cisco SFPs.
Sometimes, users will see the following in their kernel logs: [Sep24 20:53] exanic 0000:1a:00.0 enp26s0: tx timestamping failed [Sep24 22:05] exanic 0000:1a:00.0 enp26s0: tx timestamping failed [Sep24 23:55] exanic 0000:1a:00.0 enp26s0: tx timestamping...