You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was investigating an incident involves IB & PKEYs. In the collected data files, information in /$node/Infiniband/$device/pkey0 and pkey1 are missing:
No pkey found
I checked other files. IB drivers are installed correctly. so it's not likely that these 2 files are missing from the vm.
Then I checked the diagnostics.sh and figured that the file path might be wrong.
The correct path for pkey (in my case) is:
/sys/class/infiniband/mlx5_0/ports/1/pkeys/0
The script is looking for:
Line 254 if [ -f "$device/ports/pkeys/0" ]; then
The text was updated successfully, but these errors were encountered:
Looks like the problem here is that the tool doesn't account for the different filesystem structure on HC44, and that size isn't included in the testing pipeline. I'll get started fixing both of those issues.
Issue resurfaced on a custom image on an HC44. The pkey folder was found and there were pkey files in it, but the tool couldn't locate pkey 0 or pkey 1.
I was investigating an incident involves IB & PKEYs. In the collected data files, information in /$node/Infiniband/$device/pkey0 and pkey1 are missing:
No pkey found
I checked other files. IB drivers are installed correctly. so it's not likely that these 2 files are missing from the vm.
Then I checked the diagnostics.sh and figured that the file path might be wrong.
The correct path for pkey (in my case) is:
/sys/class/infiniband/mlx5_0/ports/1/pkeys/0
The script is looking for:
Line 254 if [ -f "$device/ports/pkeys/0" ]; then
The text was updated successfully, but these errors were encountered: