Hey Won, Well, I don't know if "normal" is the right phrase to use :-) From my experiences, many motherboards do report incorrect timestamps. FreeIPMI simply parses whatever information is on the motherboard. So if it is given a bad timestamp, it will output whatever that timestamp equates to.
Al On Tue, 2009-02-17 at 08:29 -0800, Won De Erick wrote: > Hi All, > > it seems that the CMOS battery is just fine. I've replicated this to several > similar boxes. > > Is this related to how freeipmi parses logs? or this is just normal? > > Thanks in advance. > > Won > > > --- On Fri, 2/13/09, Won De Erick <[email protected]> wrote: > > Hi Al, > > > > I noticed the following erroneous datestamps when viewing > > SEL. > > > > #ipmi-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 (AC/DC) > > 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. > > > > Thanks, > > > > Won > > > > -- Albert Chu [email protected] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/freeipmi-devel
