The Time of Day (TOD) on Netra X1 or Sun Fire V100 may Drift or Jump |
|
| Category : | AvailabilityData Loss |
| Release Phase : | Resolved |
| Product : | Sun Blade 2000 Workstation Sun Fire 280R Server Sun Fire V880 Server Netra X1 Server Sun Blade 1000 Workstation Sun Fire V100 Server Sun Fire V480 Server
|
| Bug Id : | 4721451, 4809862, 4997732
|
| Date of Workaround Release : | 22-NOV-2002
|
| Date of Resolved Release : | 23-MAR-2004
|
Impact
On very rare occasions the Time of Day (TOD) chip on a Netra X1 or Sun Fire V100 may be susceptible to a clock drift or jump. As a result anything that relies upon the system timer may be inaccurate. Incorrect time stamps on files could lead to database corruption and in some cases, the system may not be bootable because of the root file system's time stamp may not match the time stamp read from the system timer. Tasks monitored by the timer set like backups may also be affected.
Contributing Factors
This issue can occur in the following releases:
SPARC
-
Solaris 8 without patches 112170-02 (for BugID 4721451) and 109888-22 (for BugID 4809862)
-
Netra X1 and Sun Fire V100 (for Solaris 8) without patch 111092-04 (for BugID 4997732)
-
Solaris 9 without patches 114338-01 (for BugID 4721451) and 114126-02 (for BugID 4809862)
Note: If patch 111092-03 was installed after patch 112170-02 then the system is exposed to this issue. In this case, please backout patch 111092-03.
on the following platforms:
-
Netra X1
-
Netra 20 (Netra T4)
-
Sun Fire V100
-
Sun Blade 1000/2000
-
Sun Fire 280R
-
Sun Fire V480
-
Sun Fire V880
-
Sun Fire V880z
Symptoms
Depending on the application, there may or may not be messages that show a clock drift or jump. Messages in the /var/adm/messages file may show a jump to an incorrect timestamp like "Jan 1 07:30:02" and then at a certain point the timestamp will revert back to the correct value.
A clock drift can be verified by the messages shown below:
Oct 13 01:01:32 ffmrvrd6 [235]: [ID 702911 daemon.warning] System
clock changed by 6.003284 seconds
Oct 13 03:07:10 tibrrvd1 [228]: [ID 702911 daemon.warning] System
clock changed by 4.020005 seconds
Oct 13 05:00:31 tibctic2 [228]: [ID 702911 daemon.warning] System
clock changed by 7.016231 seconds
Workaround
There is no workaround. Please see "Resolution" section below.
Resolution
This issue is addressed in the following releases:
-
Solaris 8 with patches 112170-02 and 109888-22 or later
-
Netra X1 and Sun Fire V100 (for Solaris 8) with patch 111092-04 or later
-
Solaris 9 with patches 114338-01 and 114126-02 or later
Note: Please see the above patch READMEs for patch dependencies and installation instructions.
Modification HistoryDate: 03-FEB-2003
Date: 27-MAR-2003
-
Added BugID 4809862
-
Added additional affected systems to Contributing Factors
Date: 25-APR-2003
-
Updated Contributing Factors and Resolution sections
Date: 30-MAY-2003
-
Updated Contributing Factors and Resolution sections
Date: 16-JUL-2003
-
Updated Contributing Factors and Resolution sections
Date: 08-AUG-2003
-
Updated Contributing Factors
Date: 29-AUG-2003
-
Updated Contributing Factors and Resolution sections
Date: 23-MAR-2004
-
State: Resolved
-
Updated BugID list
-
Updated Contributing Factors and Resolution sections
Date: 26-MAR-2004
-
Updated Contributing Factors with "Note"
AttachmentsThis solution has no attachment