| Summary: | RTC inaccuracy issue found on both Kraken and Intel CRB. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Ducky Lin <Ducky.Lin> |
| Component: | kernel | Assignee: | Prarit Bhargava <prarit> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0 | CC: | arozansk, checa92 |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-30 14:03:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Ducky Lin
2011-03-18 07:12:51 UTC
//******** Issue Description: RHEL 6 Sytem time inaccuracy Description of problem: NTP is not used in this case on purpose. After leaving system idle for seven days, the system time would drift around half hour on RHEL 6, while RHEL 5.5 and SLES 11 are fine. Steps to Reproduce: 1. Install Linux OS RHEL6. 2. Leave system idle, the system time retrieved by command “date” would drift over time against HW RTC time "hwclock". 3. By comparing one of internet clock, we’re confident the HW RTC time is accurate enough within the test time. 4. So it’s system clock that drift. Actual results: After system idle on seven days, the system time would drift around half hour. Symptom on other OS: System clock on RHEL 5.5, SLES 11 and even Windows does keep up with HW RTC and internet clock. Expected results: The system clock would keep up with either HW RTC or internet clock just like other OS release. ********// (In reply to comment #0) > Description of problem: > After finishing Warm Boot on seven days, RTC time is faster than helf hour on > Linux OS > Version-Release number of selected component (if applicable): > RHEL Kernel version: 2.6.32-71.el6.x86_64 > How reproducible: > Steps to Reproduce: > 1. Boot into BIOS set HDD AHCI-leagcy. > 2. Install Linux OS then update LAN and VGA driver. > 3. Vi /etc/inittab to edit linux to txt mode > 4. Vi /etc/rc.local to type "sleep 10" and "reboot" to run Warm boot > 5. Start Power cycle > Actual results: > After doing Warm Boot on seven days, RTC time is faster than helf hour on OS. > Expected results: > After doing Warm Boot on seven days, RTC time doesn't faster or slower on OS. > Additional info: Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Since RHEL 6.2 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Ducky Lin, OOC what clock (TSC, HPET, PMTIMER) are you using? P. |