This document contains the NI Linux Device Drivers known issues that were discovered before and since the release of NI Linux Device Drivers 2022 Q2. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
System Crashes When NI Drivers Exceed the Default Max for iNotify Instances
When running code that initializes NI drivers, the system crashes. This may be because the NI drivers have requested more than the 128 iNotify instances that the default Linux kernel allows. The likelihood of encountering this issue increases as the number of installed drivers increases.
Increase the iNotify limit from the default 128 to a larger number, such as 12288.
You can increase the iNotify limit permanently through the following:
fs.inotify.max_user_instances=<Upper Limit> to /etc/sysctl.conf
to reload the limit
sysctl -a | grep fs.inotify.max_user_instances
to see that the new limit is set.
Or you can increase the iNotify limit after every restart with this command: