Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionsushil kulkarni
2019-03-14 15:41:30 UTC
More details:
https://docs.engineering.redhat.com/pages/viewpage.action?pageId=63300108
User Story:
As a 5G cRAN edge cloud provider, I need accurate sub-microsecond PTP clock timing accuracy on RHEL8 with RHEL-RT and RT-KVM in order to deploy cRAN applications on RHEL
verify RHEL timing accuracy < 130ns and offset error is few ns
IPv4/UDP Unicast and 2-Way messaging
Usecase 1- Ordinary Clock (GM and Slave only)
Measure Timing accuracy on RHEL host and guest with error offset and plot over 24 hour duration
Since we could get the real accuracy of the system. Set as SanityOnly.
maxOffset minOffset rmsOffset maxDelay minDelay rmsDelay
Ptp4l 14258 0 266 316 281 293
Phc2sys 162 0 13 511 367 483
the max estimated error in host is 908.5ns
the max estimated error in guest is 55.707ns
Host info:
[root@hp-dl380g10-04 errorCalc]# uname -r
4.18.0-134.rt24.79.el8.x86_64
[root@hp-dl380g10-04 errorCalc]# ethtool -i ens2f0
driver: mlx5_core
version: 5.0-0
firmware-version: 16.25.1020 (MT_0000000080)
expansion-rom-version:
bus-info: 0000:37:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes
[root@hp-dl380g10-04 errorCalc]# lspci -s 37:00.0
37:00.0 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5]
[root@hp-dl380g10-04 errorCalc]#
Guest info:
[root@localhost ~]# uname -r
4.18.0-134.rt24.79.el8.x86_64
[root@localhost ~]#
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2019:3380