Re: IPMI fix for panic handling

[Randy.Dunlap]

On Thu, 21 Aug 2003 11:53:31 -0500 Corey Minyard <cminyard@xxxxxxxxxx> wrote:

| >diff -u -r1.3 Kconfig
| >--- drivers/char/ipmi/Kconfig	28 Mar 2003 05:14:18 -0000	1.3
| >+++ drivers/char/ipmi/Kconfig	19 Aug 2003 14:20:43 -0000
| >@@ -24,6 +24,18 @@
| > 	 generate an IPMI event describing the panic to each interface
| > 	 registered with the message handler.
| > 
| >+config IPMI_PANIC_STRING
| >+	bool 'Generate a OEM events holding the panic string'
| >
| >I can't decode/translate that quoted string...
| >'an OEM event' ??
| >s/holding/containing/ ??
| >
| I'll work on that.  Is the description below good enough?

Yes, I think it is.

| >
| >+	depends on IPMI_PANIC_EVENT
| >+	help
| >+	  When a panic occurs, this will cause the IPMI message handler to
| >+	  generate an IPMI OEM type f0 events holding the IPMB address of the
| >                                       event
| >+	  panic generator (byte 4 of the event), a sequence number for the
| >+	  string (byte 5 of the event) and part of the string (the rest of the
| >+	  event).  Bytes 1, 2, and 3 are the normal usage for an OEM event.
| >+	  You can fetch these events and use the sequence numbers to piece the
| >+	  string together.
| >+
| > config IPMI_DEVICE_INTERFACE
| >        tristate 'Device interface for IPMI'
| >        depends on IPMI_HANDLER

--
~Randy   [mantra:  Always include kernel version.]
"Everything is relative."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/