cRIO9040 crash

[Ghis]

Hi guys
I have a problem with my crio9040.
Indeed, for several weeks I have not been able to identify a crash of this one for no apparent reason.
My log file generate by my program because i have a hardware crash.

When I look at the cRIO log in NImax, it informs me of this but I'm not sure that's the problem:

Kernel log:

"2023-07-21T00:00:41.352+02:00 BPP2 kernel: [28355.542124] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
2023-07-21T00:00:41.392+02:00 BPP2 kernel: [28355.580251] CIFS: VFS: parse_server_interfaces: malformed interface info"

On restart.

Error log:

"####
#Date: Fri, Jul 21, 2023 08:39:32 AM
#OSName: Linux
#OSVers: 5.15.113-rt64
#OSBuild: 331633
#AppName: lvrt
#Version: 21.0f3
#AppKind: AppLib
#AppModDate: 

InitExecSystem() call to GetCurrProcessNumProcessors() reports: 2 processors
InitExecSystem() call to GetNumProcessors()            reports: 2 processors
InitExecSystem()                                      will use: 2 processors
starting LV_ESys1248001a_Thr0 , capacity: 24 at [3772766387.42935610, (08:39:47.429356000 2023:07:21)]
starting LV_ESys2_Thr0 , capacity: 24 at [3772766387.49391699, (08:39:47.493917000 2023:07:21)]
starting LV_ESys2_Thr1 , capacity: 24 at [3772766387.49391699, (08:39:47.493917000 2023:07:21)]
starting LV_ESys2_Thr2 , capacity: 24 at [3772766387.49391699, (08:39:47.493917000 2023:07:21)]
starting LV_ESys2_Thr3 , capacity: 24 at [3772766387.49391699, (08:39:47.493917000 2023:07:21)]"

 

I network a record file at some point, hence the CIFS:

"mount -t cifs //networkpath -o username=name ,password=password,uid=admin, vers=1.0 localpath"

I have another test bench that uses this function without crashing.

does anyone have any idea how to find the problem?

thanks !

[Jordan Kuehn]

If you have a current service agreement I would suggest taking this to NI directly if you haven't yet.

https://sine.ni.com/srm/app/myServiceRequests