[Freeipmi-devel] RE: ipmi-dcmi testing results

[Liebig, Holger]

> > --get-power-limit:
> > The exception action is not a bit field and OEM actions are 
> only defined for values 0x02 ... 0x10.
> 
> Thanks.  I actually had a note in my printed copy of the spec 
> with a question mark next to it b/c I couldn't tell if it was 
> values or bitmasks.  I obviously guessed wrong :-)
> 

Some more testing with the 0.8.2beta3 shows, that after deactivating the power 
limit, the --get-power-limit is choking on the completion code 0x80 (Power 
Limit not active), also a --set-power-limit --power-limit-requested=350 is 
reading the current setting before modifying the settings and also fails when 
the power limit is disabled. The typical use case is more like configure 
some/all settings, and then activate the power limit. Decoding of the 'out of 
range' completion codes would be helpful for end users (unfortunately there is 
currently no way to get the actual limits from the BMC other than with trial 
and error). 

The attached small patch activates correct packet decoding with --debug for 
DCMI commands, and corrects the --set-power-limit command template which had 
only a 3byte correction time instead of 32bits.

Holger

P.S. Regarding OEM exception action we currently do support 'continue' (0x02) 
and 'shutdown' (0x03) in addition to the 'hard power off'. So it would be 
helpful to have the manufacturer_id and product_id around in a later version. 
What are the chances to get this added to the ipmi_ctx structure for general 
availability in all of the tools?

dcmi_0.8.2b3.patch
Description: dcmi_0.8.2b3.patch