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.
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:
//********
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 3RHEL 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 4RHEL 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.