Lines Matching refs:the

9  watchdog functionality and the added benefit of NMI sourcing. Both the
10  watchdog functionality and the NMI sourcing capability need to be enabled
11  by the user. Remember that the two modes are not dependent on one another.
12  A user can have the NMI sourcing without the watchdog timer and vice-versa.
15  is, an application needs to be started that kicks off the watchdog timer. A
16  basic application exists in the Documentation/watchdog/src directory called
17  watchdog-test.c. Simply compile the C file and kick it off. If the system
18  gets into a bad state and hangs, the HP ProLiant iLO 2 timer register will
22  The hpwdt driver also has four (4) module parameters. They are the following:
24  soft_margin - allows the user to set the watchdog timer value
25  allow_kdump - allows the user to save off a kernel dump image after an NMI
26  nowayout    - basic watchdog parameter that does not allow the timer to
28  priority    - determines whether or not the hpwdt driver is first on the
30                for this module parameter is 0 or LAST. If the user wants to
31                enable NMI sourcing then reload the hpwdt driver with
34  NOTE: More information about watchdog drivers in general, including the ioctl
40  enables the users of NMIs for non critical events to be work as expected.
42  The NMI sourcing capability is disabled by default due to the inability to
43  distinguish between "NMI Watchdog Ticks" and "HW generated NMI events" in the
44  Linux kernel. What this means is that the hpwdt nmi handler code is called
45  each time the NMI signal fires off. This could amount to several thousands of
46  NMIs in a matter of seconds. If a user sees the Linux kernel's "dazed and
47  confused" message in the logs or if the system gets into a hung state, then
48  the hpwdt driver can be reloaded with the "priority" module parameter set
51  1. If the kernel has not been booted with nmi_watchdog turned off then
52     edit /boot/grub/menu.lst and place the nmi_watchdog=0 at the end of the
54  2. reboot the sever
55  3. Once the system comes up perform a rmmod hpwdt
58  Now, the hpwdt can successfully receive and source the NMI and provide a log
59  message that details the reason for the NMI (as determined by the HP BIOS).
61  Below is a list of NMIs the HP BIOS understands along with the associated