Background: This (Kernel warning "jump label: negative count") post presents a kernel bug in Drive OS 5.2.0 that causes /var/log/kern.log and /var/log/syslog to be spammed with repeated errors from the kernel saying jump label: negative count among other info. That post provides a patch and instructions to fix the bug. We have been seeing a very similar looking error on systems running Drive OS 5.2.6.
My Question Did Nvidia fix the bug that linked post refers to in the Drive OS 5.2.6 release? I checked the source code and nvmap_init_t19x.c and nvmap_cache_t19x.c do not change between the 5.2.0 and 5.2.6 releases, but perhaps the bug was fixed elsewhere? I am wondering because I would like to know whether applying this patch as described in that post to the 5.2.6 release is recommended.
Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other
Target Operating System
Linux
QNX
other
Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other
SDK Manager Version
1.9.1.10844
other
Host Machine Version
native Ubuntu 18.04
other