Description

We see the below logs on VRR:

jlock (W) hog reported for 1140 msecs: time_uptime (acq=3160057, rel=3160058), ticks (acq=1011973055, rel=1011974195), net_jlock_uptime (acq=3160029, rel=3160030) td 0xfffff800064ea760 (dcd): td_prio 121, pri_promo 0, CPU 3, td_lastrt 1011973428, jlock (acq=1011973055, cur=1011974195): offending fns (acq=rts_usr_send(), rel=rts_usr_send()). td_runtime 1140503 usecs, nvcsw 0, nivcsw 1

 

Symptoms

Mar 12 23:48:30   kernel: %KERN-3: pointchange for TLV type 00000020 not supported on IFD em1
Mar 12 23:48:30   kernel: %KERN-3: pointchange for TLV type 00000020 not supported on IFD em2
Mar 12 23:48:30   kernel: %KERN-2: ixv1: There is a problem with the PF setup.  It is likely the receive unit for this VF will not function correctly.
Mar 12 23:48:30   kernel: %KERN-2: ixv1: There is a problem with the PF setup.  It is likely the receive unit for this VF will not function correctly.
Mar 12 23:48:30   kernel: %KERN-3: rts_output_idl: VKS0: M, VKS1: M, rts_msgproc[type=6], hogtime=1140 ms, op=8, curthread dcd, sender_id=0, err=-1
Mar 12 23:48:30   kernel: %KERN-3: jlock (W) hog reported for 1140 msecs: time_uptime (acq=3160057, rel=3160058), ticks (acq=1011973055, rel=1011974195), net_jlock_uptime (acq=3160029, rel=3160030) td 0xfffff800064ea760 (dcd): td_prio 121, pri_promo 0, CPU 3, td_lastrt 1011973428, jlock (acq=1011973055, cur=1011974195): offending fns (acq=rts_usr_send(), rel=rts_usr_send()). td_runtime 1140503 usecs, nvcsw 0, nivcsw 1 (../../../../../../../../../src/junos/bsd/sys/netrtsock/rtsock_common.c, line 5119): { 0xffffffff812e1aef 0xffffffff812e7c9a 0xffffffff812e84fe 0xffffffff8178dc61 0xffffffff8052cac1 0xffffffff8178de96 0xffffffff8050bae2 0xffffffff80503405 0xffffffff805

 

Solution


we observed that the Kernel logs appeared on VRR platform after initiating the commit or commit confirmed on the chassis. Additionally, the Kernel logs are informational and categorized as debug-level messages, indicating that the kernel was occupied processing sampled traffic. The "Jlock" messages suggest that the CPU was engaged in other tasks, such as handling configuration changes, where certain processes or functions required CPU cycles acquired via the jlock mechanism. Typically, a brief duration of jlock hogging does not impact system performance.

Modification History

2024-06-27 : Article Created