[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Freeipmi-devel] Re: ibmx3650 reboots after ipmi-sel is unable toget
From: |
Won De Erick |
Subject: |
RE: [Freeipmi-devel] Re: ibmx3650 reboots after ipmi-sel is unable toget SEL record |
Date: |
Wed, 18 Mar 2009 22:36:45 -0700 (PDT) |
--- On Wed, 3/18/09, Al Chu <address@hidden> wrote:
> Hey Won,
>
> As Andrew said, we need a bit more information. For
> freeipmi, you could
> output the SEL in hex (-x), but for what we're trying to
> do, it might be
> best to output with --debug. You'll be able to see
> the SEL Event
> Records before each output. We can interpret the hex
> from that point.
>
> Al
I'll get back with the debug output later.
>
> On Wed, 2009-03-18 at 06:55 -0700, Andy Cress wrote:
> > Won,
> >
> > This needs more information.
> > A raw dump of the SEL would help to determine whether
> > the problem is in
> > the freeipmi interpretation or a problem on the
> > server.
> > To get a raw dump of the SEL:
> > ipmiutil sel -r
> > sel.raw
> > ipmitool sel writeraw sel.raw
> > (not sure of how to do this
> > with freeipmi)
> >
> > If this record has event data 1 == 0x80, then "System
> > Reconfigured" is a
> > good interpretation.
> > If it is interpreted correctly, then the SEL records
> > surrounding this
> > event need to be reviewed.
> > Also, if you got this event, then there may be some
> > ipmi-related
> > processes running that caused it (output of ps
> > -ef).
> >
> > Andy
I remember I had a problem installing ipmiutil in FreeBSD from ports. It was
looking for some dependencies. iirc, related to ipmi driver.
Does the tool fully support FreeBSD?