[prev in list] [next in list] [prev in thread] [next in thread]
List: freeipmi-users
Subject: Re: [Freeipmi-users] Internal IPMI error
From: Al Chu via Freeipmi-users <freeipmi-users () gnu ! org>
Date: 2019-11-18 16:42:00
Message-ID: 652d80f257ef9282de8aef852d28ec9779bd5699.camel () llnl ! gov
[Download RAW message or body]
Hi Thomas,
Ahhh, so what you're saying is FreeIPMI gets the error and doesn't
continue to output additional FRU information?
There is a expected error code for when information from the
motherboard isn't available (I can't remember that expected code at the
moment), so I guess your motherboard isn't reporting that error code.
Let me work up a workaround for you to try and I'll e-mail you with a
branch path.
Al
On Mon, 2019-11-18 at 15:27 +0000, Thomas Perschak wrote:
> Hi Albert,
>
> thx for your support.
>
> It's not that it does not read the FRU, the ipmi-fru command reads
> the chassis, mainboard and some other data, but then it stops with
> the error.
> Here below what the other tools do:
>
> The ipmiutil fru command returns with an error (after some correct
> output):
> ...
> [Baseboard,20,00] System GUID : 44457349-141b-6eb2-4094-
> c20224ea2049
> Can't find SMBIOS address entry point.
>
>
> The ipmitool fru command reports a device not present, but no error:
> ...
> FRU Device Description : PSU STD (ID 4)
> Device not present (Command response could not be provided)
>
>
>
> Regards
> Thomas
>
>
> From: Albert Chu <chu11@llnl.gov>
> Sent: 15 November 2019 18:15
> To: Thomas Perschak <tombert.group@live.at>; freeipmi-users@gnu.org <
> freeipmi-users@gnu.org>
> Subject: Re: [Freeipmi-users] Internal IPMI error
>
> Hi Thomas,
>
> Hmmm. The CEh error code corresponds to "Command response could not
> be
> provided". So it's possible your motherboard doesn't provide this
> functionality? It would be strange for a modern system to not
> provide
> basic FRU functionality, so it's possible there's a more fundamental
> issue. Perhaps the firmware is bad?
>
> Another possibility is that the firmware has a bug that it doesn't
> recognize the Read FRU Data Request format. Does any other IPMI
> software read the FRU correctly?
>
> Al
>
> On Fri, 2019-11-15 at 10:14 +0000, Thomas Perschak wrote:
> > Hi IPMI users,
> >
> > I got an internal error on the following server:
> >
> > Fujitsu Primergy RX1330, Ubuntu 18, ipmi-fru 1.4.11
> >
> > =====================================================
> > Read FRU Data Response
> > =====================================================
> > [ 11h] = cmd[ 8b]
> > [ CEh] = comp_code[ 8b]
> > ipmi_fru_open_device_id: internal IPMI error
> >
> >
> > How can I support to fix this issue?
> >
> > thx!
> > _______________________________________________
> > Freeipmi-users mailing list
> > Freeipmi-users@gnu.org
> > https://lists.gnu.org/mailman/listinfo/freeipmi-users
_______________________________________________
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic