[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log
From: |
Al Chu |
Subject: |
Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log |
Date: |
Tue, 07 Feb 2012 07:44:33 -0800 |
Hey Gotz,
> "0x00 0xFF 0xFF"
> > "0x01 0xFF 0xFF"
> > "0x03 0xFF 0xFF"
Could you try a few more 0x04-0x0F
"0x04 0xFF 0xFF"
"0x05 0xFF 0xFF"
...
"0x0E 0xFF 0xFF"
"0x0F 0xFF 0xFF"
I suppose it's possible the Supermicro motherboards only report
overheats in the SEL but nothing self.
Al
On Tue, 2012-02-07 at 02:20 -0800, Götz Waschk wrote:
> On Mon, Feb 6, 2012 at 7:06 PM, Albert Chu <address@hidden> wrote:
> > To create SEL events, we can use bmc-device and the --platform-event
> > option. I think the following would be the equivalent to what you've
> > seen before:
> >
> > bmc-device --platform-event="0x20 0x04 0xC0 0x02 0x70 deassertion 0x02
> > 0xFF 0xFF"
> >
> > of what has been generated so far. If you can change the
> >
> > "0x02 0xFF 0xFF"
> >
> > to
> >
> > "0x00 0xFF 0xFF"
> > "0x01 0xFF 0xFF"
> > "0x03 0xFF 0xFF"
> > ...
> >
> > and etc. we can reverse engineer the remaining mappings.
> Hmm, I have tried it, but the results were not as expected:
>
> # bmc-device --platform-event="0x20 0x04 0xC0 0x02 0x70 deassertion
> 0x00 0xFF 0xFF"
> # bmc-device --platform-event="0x20 0x04 0xC0 0x02 0x70 deassertion
> 0x01 0xFF 0xFF"
> # bmc-device --platform-event="0x20 0x04 0xC0 0x02 0x70 deassertion
> 0x03 0xFF 0xFF"
>
> 10 | Feb-07-2012 | 12:17:02 | Sensor #2 | OEM Reserved | OEM
> Event Offset = 00h
> 11 | Feb-07-2012 | 12:17:07 | Sensor #2 | OEM Reserved | OEM
> Event Offset = 01h
> 12 | Feb-07-2012 | 12:17:10 | Sensor #2 | OEM Reserved | OEM
> Event Offset = 03h
>
> RID:[0A][00] RT:[02] TS:[2E][08][31][4F] GID:[21][00] ER:[04] ST:[C0]
> SN:[02] EDIR:[F0] ED1: [00] ED2: [FF] ED3: [FF]
> RID:[0B][00] RT:[02] TS:[33][08][31][4F] GID:[21][00] ER:[04] ST:[C0]
> SN:[02] EDIR:[F0] ED1: [01] ED2: [FF] ED3: [FF]
> RID:[0C][00] RT:[02] TS:[36][08][31][4F] GID:[21][00] ER:[04] ST:[C0]
> SN:[02] EDIR:[F0] ED1: [03] ED2: [FF] ED3: [FF]
>
> and with the Supermicro tool:
> Event:10 Time:02/07/2012 11:17:02 Type:OEM
> CPU2 Temp De-assertion: undefined
> ------------------------------------------------------------------
> Event:11 Time:02/07/2012 11:17:07 Type:OEM
> CPU2 Temp De-assertion: undefined
> ------------------------------------------------------------------
> Event:12 Time:02/07/2012 11:17:10 Type:OEM
> CPU2 Temp De-assertion: undefined
>
> Regards, Götz
>
--
Albert Chu
address@hidden
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
- Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log, Werner Fischer, 2012/02/06
- Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log, Götz Waschk, 2012/02/06
- Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log, Albert Chu, 2012/02/06
- Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log, Götz Waschk, 2012/02/07
- Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log,
Al Chu <=
- Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log, Götz Waschk, 2012/02/07
- Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log, Al Chu, 2012/02/07
- Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log, Al Chu, 2012/02/07
- Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log, Götz Waschk, 2012/02/08
- Re: [Freeipmi-devel] Supermicro X8DTG-QF System Event Log, Albert Chu, 2012/02/08