Ipmi firmware user guide: am4010 – Kontron AM4010 User Manual
Page 30
IPMI Firmware User Guide: AM4010
During Hot Swap of a working module the payload side has to be shut down automatically on
command of the MMC and the end of shut down has to be signalled back to the MMC.
Because the AM4010 supports ACPI, an OS on payload side which supports this too makes
shut down very easy. If the OS doesn’t support ACPI there is a special method to be used.
Method 1. The payload OS supports ACPI
Requirements:
• ACPI support must be enabled in the BIOS menu.
• The ACPI daemon must be active.
• An ACPI power button event must result in a sleep state.
Part of the Hot Swap 0peration sequence to be processed by MMC and OS:
• On command of the carrier controller the MMC simulates the pressing and release of
the “power button” to force an ACPI event.
• The ACPI daemon detects this ACPI event and initiates the shut down of the payload
software system.
• At the end of shut down the payload hardware system reports the sleep state to the
MMC by setting the appropriate signal line.
• The MMC detects the sleep state and reports this to the carrier controller so that the
Hot Swap processing can be continued and finished.
By default the MMC waits endless for the sleep state. If an endless wait shall be avoided
in each case it is possible to set a timeout time after which the system will be switched off
unconditionally. For the setting of the timeout refer to 6.2.2.5,
Method 2. The payload OS does not support ACPI
Requirements:
• At system start on payload side the Kontron shutdown daemon ‘grnsd’ has to be
started. It is included in the Linux board support packages for the AM4010 (refer to
[
]). This daemon communicates cyclically with the MMC for the exchange of states,
commands and acknowledges. For this it uses the “
” command. Refer to 6.2.2.5. In principle it plays the same role as the ACPI
daemon of method 1, above.
Part of the Hot Swap 0peration sequence to be processed by MMC and OS:
• On command of the carrier controller the MMC sets a “shut down request” flag.
• The grnsd daemon recognizes this request in the response to its cyclical “
” command and initiates the shut down of the payload
software system.
• At the end of the shut down process the grnsd daemon informs the MMC by setting
the appropriate flag when calling the “
OEM Module Quiescence Feedback
” command.
• The MMC reports this to the carrier controller so that the Hot Swap processing can be
continued and finished.
By default the MMC waits endless for this information. If an endless wait shall be avoided
in each case it is possible to set a timeout time after which the system will be switched off
unconditionally. For the setting of the timeout refer to 6.2.2.5,
Page
30
© 2007 Kontron AG
ID: 36363, Rev. 1.1