Lines Matching full:panic

80 If you want the driver to put an event into the event log on a panic,
81 enable the 'Generate a panic event to all BMCs on a panic' option.  If
82 you want the whole panic string put into the event log using OEM
83 events, enable the 'Generate OEM events containing the panic string'
583 this driver cannot do IPMI panic events, extend the watchdog at panic
584 time, or other panic-related IPMI functions without special kernel
675 is the amount of seconds before the reset that the pre-timeout panic will
680 is the value of timeout which is set on kernel panic, in order to let actions
681 such as kdump to occur during panic.
693 "preop_panic" to set the preoperation to panic, or "preop_give_data"
722 The watchdog will panic and start a 120 second reset timeout if it
723 gets a pre-action.  During a panic or a reboot, the watchdog will
729 otherwise unhandled NMI, it must be from IPMI and it will panic
738 Panic Timeouts
742 events in the system event log if a panic occurs.  if you enable the
743 'Generate a panic event to all BMCs on a panic' option, you will get
744 one event on a panic in a standard IPMI event format.  If you enable
745 the 'Generate OEM events containing the panic string' option, you will
746 also get a bunch of OEM events holding the panic string.
754 * Sensor #: The first byte of the panic string (0 if no panic string)
757 * Event data 2: second byte of panic string
758 * Event data 3: third byte of panic string
768 * byte 3: The slave address of the card saving the panic
770   The rest of the bytes (11 bytes) are the panic string.  If the panic string