Bug 688833 - RTC inaccuracy issue found on both Kraken and Intel CRB.
Summary: RTC inaccuracy issue found on both Kraken and Intel CRB.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Prarit Bhargava
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-18 07:12 UTC by Ducky Lin
Modified: 2012-04-30 14:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-30 14:03:13 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ducky Lin 2011-03-18 07:12:51 UTC
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:

Comment 2 Checa Hung 2011-03-24 05:10:01 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:

Comment 3 RHEL Program Management 2011-04-04 02:45:23 UTC
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.

Comment 4 RHEL Program Management 2011-10-07 15:27:07 UTC
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.

Comment 5 Prarit Bhargava 2012-01-04 19:11:41 UTC
Ducky Lin, OOC what clock (TSC, HPET, PMTIMER) are you using?

P.


Note You need to log in before you can comment on or make changes to this bug.