RE: [Ipmitool-devel] Question about SEL timestamps

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Just for grins I set my BIOS clock ahead 24 hours, and sure enough the =
SEL events come back with today's date.  It shows up after the second =
"Clock sync" event, which occurs when I reboot the machine.  The date =
goes from Feb 22 to Feb 23.

 edc | 02/22/2005 | 10:22:00 | System Event #0x83 | Timestamp Clock =
Sync.
 ef0 | 02/23/2005 | 10:22:01 | System Event #0x83 | Timestamp Clock =
Sync.
 f04 | 02/23/2005 | 10:22:19 | System Event #0x83 | OEM System boot =
event

Is this peculiar to the Intel motherboard or am I missing something?

John

> -----Original Message-----
> From: Jon Cassorla [mailto:jon...@ne...]
> Sent: Wednesday, February 23, 2005 4:10 PM
> To: Fusco, John (GE Healthcare); ipm...@li...
> Subject: RE: [Ipmitool-devel] Question about SEL timestamps
>=20
>=20
>=20
> Looks to me as though things worked ok with your command. =20
> When you set the time, there are two events logged in the=20
> SEL.  The first is the time prior to your command taking=20
> effect, the second is the new time.
>=20
> > -----Original Message-----
> > From: ipm...@li...
> > [mailto:ipm...@li...]On=20
> Behalf Of Fusco,
> > John (GE Healthcare)
> > Sent: Wednesday, February 23, 2005 3:17 PM
> > To: ipm...@li...
> > Subject: RE: [Ipmitool-devel] Question about SEL timestamps
> >=20
> >=20
> >=20
> >=20
> > > -----Original Message-----
> > > From: Duncan Laurie [mailto:du...@ic...]
> > > Sent: Wednesday, February 23, 2005 2:33 PM
> > > To: Fusco, John (GE Healthcare)
> > > Cc: ipm...@li...
> > > Subject: RE: [Ipmitool-devel] Question about SEL timestamps
> > >=20
> > >=20
> > > On Wed, 2005-02-23 at 14:26 -0600, Fusco, John (GE=20
> > Healthcare) wrote:
> > > >=20
> > > > Here is the SEL record printed by ipmitool.  Note that it=20
> > > is off by one day + 6 hours.
> > > >  e14 | 02/22/2005 | 07:33:05 | System Event #0x83 | OEM=20
> > > System boot event
> > > >=20
> > > > If I read this record out using the raw interface, the time=20
> > > value is 1109079185, which in local time agrees with the SEL=20
> > > message from ipmitool.
> > > >=20
> > > > Any ideas?  I would like to make use of the SEL, but if the=20
> > > dates and times are wrong, then the data is useless.
> > > >=20
> > >=20
> > > Any chance you can set the SEL time with ipmitool?
> > >=20
> > > # ipmitool -I open sel time get
> > > 01/01/2002 13:33:46
> > >=20
> > > # ipmitool -I open sel time set "$(date +'%m/%d/%Y %H:%M:%S')"
> > >=20
> > > # ipmitool -I open sel time get
> > > 02/23/2005 13:30:56
> > >=20
> > > I forget when these commands went in, if they are not in=20
> > > 1.6.0 then you
> > > can try CVS or the 1.7.0rc3 snapshot at ipmitool.sf.net/snapshot
> >=20
> >=20
> > I was able to get the snapshot and use the 'sel time set'=20
> > command to set the clock to local time.  It seemed to work,=20
> > so I rebooted and checked the event log.  Read on...
> >=20
> >  e28 | 02/23/2005 | 15:00:08 | System Event #0x83 | Timestamp=20
> > Clock Sync.
> >  e3c | 02/22/2005 | 09:01:42 | System Event #0x83 | Timestamp=20
> > Clock Sync.
> >  e50 | 02/22/2005 | 09:02:00 | System Event #0x83 | OEM=20
> > System boot event
> >=20
> > Something set the clock back!  Is there a separate step to=20
> > make the clock change permanent?
> >=20
> > John
> >=20
> >=20
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from=20
> > real users.
> > Discover which products truly live up to the hype. Start=20
> reading now.
> > http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dick
> > _______________________________________________
> > Ipmitool-devel mailing list
> > Ipm...@li...
> > https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
> >=20
>=20