-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.8
-
None
-
None
-
Moderate
-
rhel-net-core
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
What were you trying to do that didn't work?
if I run dpll monitor in background and redirect output to a log file, sometimes the dpll notification can't be sent to log file
What is the impact of this issue to you?
Please provide the package NVR for which the bug is seen:
[root@dell-per740-91 iproute]# dpll -V
dpll utility, iproute2-6.17.0
[root@dell-per740-91 iproute]# rpm -q iproute
iproute-6.17.0-2.el9.x86_64
[root@dell-per740-91 iproute]# uname -r
5.14.0-658.el9.x86_64
How reproducible is this bug?:
always
Steps to reproduce
1. make sure the GNSS pin is enabled and dpll locked to GNSS input [root@dell-per740-91 iproute]# dpll pin set id 6 parent-device 0 state selectable [root@dell-per740-91 iproute]# dpll pin set id 6 parent-device 1 state selectable [root@dell-per740-91 iproute]# dpll device show device id 0: module-name: ice mode: automatic clock-id: 5799633565437511660 type: eec lock-status: locked-ho-acq mode-supported: automatic device id 1: module-name: ice mode: automatic clock-id: 5799633565437511660 type: pps lock-status: locked mode-supported: automatic 2. start dpll monitor in background [root@dell-per740-91 iproute]# dpll monitor &>log & [1] 134372 3. disable GNSS pin, and dpll changed to holdover state [root@dell-per740-91 iproute]# dpll pin set id 6 parent-device 1 state disconnected [root@dell-per740-91 iproute]# dpll pin set id 6 parent-device 0 state disconnected [root@dell-per740-91 iproute]# dpll device show device id 0: module-name: ice mode: automatic clock-id: 5799633565437511660 type: eec lock-status: holdover mode-supported: automatic device id 1: module-name: ice mode: automatic clock-id: 5799633565437511660 type: pps lock-status: holdover mode-supported: automatic 4. check the log, there is no relevant notification(DEVICE_CHANGE) in the log file, I will attache the log file. the lock status change notification was not wrote to log file.
