Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-59582

[release-4.18]Clock Accuracy is not explicitly set in 4.16

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Hi ,

      As discussed we check in logs that we are announcing 0x27 clock accuracy which is wrong to what we set in T-GM Suite code (we set 0x21) that why its saying illegal clock accuracy , Going further we observed that Clock Accuracy is not explicitly set in 4.16.

      "data":{"timestamp":"2025-06-22T08:34:20.27868893Z","timeSource":"0x20","clockAccuracy":"0x27","offsetScaledLogVariance":"0x4e5d","clock_class":6,"currentUtcOffset":37,"leap61":0,"leap59":0,"currentUtcOffsetValid":1,"ptpTimescale":1,"timeTraceable":1,"frequencyTraceable":1},"id":"phc/gm-settings"}
{"data":{"eecstate":"3","eecterror":0,"state":"3","terror":3.622,"timestamp":"2025-06-22T08:34:20.277615739Z"},"id":"dpll/time-error"}
{"data":{"ferror":173,"flags":"0xdd","state":5,"terror":3,"timestamp":"2025-06-22T08:34:20.2411Z"},"id":"gnss/time-error"}

      Logs attached

              vgrinber@redhat.com Vitaly Grinberg
              vkhokhar varun khokhar
              None
              None
              varun khokhar varun khokhar
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: