I've noticed some timestamps like that on some of my machines before.
The previous times I've noticed it, the system is storing an invalid
date (and subsequently ipmi-sel converts it to the appropriate local
time). I assume it's some hardware issue.
If you do a --debug and grep for "timestamp". You can see if some of
the timestamps are *way* off from the other ones.
On Thu, 2009-02-12 at 23:53 -0800, Won De Erick wrote:
> Hi Al,
> I noticed the following erroneous datestamps when viewing SEL.
> 144:08-Feb-2009 03:51:08:System Event System Event:Timestamp Clock Synch
> 164:08-Feb-2009 03:51:03:System Event System Event:Timestamp Clock Synch
> 184:08-Feb-2009 03:51:25:System Event System Event:OEM System Boot Event
> 444:01-Jan-1970 08:00:11:Power Supply Power Supply 2:Power Supply input lost
> 464:01-Jan-1970 08:00:12:Power Unit Power Redundancy:Entered from
> Non-redundant:Insufficient Resources
> 484:01-Jan-1970 08:00:50:System Event System Event:Timestamp Clock Synch
> 504:10-Feb-2009 11:45:09:System Event System Event:Timestamp Clock Synch
> I've replicated this to several machines. Though the CMOS battery could be
> the potential reason, I want to know if ipmi-sel is related to this, or has
> something to do with this.
High Performance Systems Division
Lawrence Livermore National Laboratory
Freeipmi-devel mailing list