linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ville Herva <vherva@niksula.hut.fi>
To: Marcelo Tosatti <marcelo@conectiva.com.br>, torvalds@osdl.org
Cc: lkml <linux-kernel@vger.kernel.org>, ak@suse.de
Subject: [PATCH] NMI watchdog documentation
Date: Wed, 23 Jul 2003 20:43:25 +0300	[thread overview]
Message-ID: <20030723174325.GL150921@niksula.cs.hut.fi> (raw)

Documentation/nmi-watchdoc.txt doesn't actually tell what options need to be
enabled in kernel config in order to use NMI watchdog. I for one found it
confusing.

I vaguely recall someone posted a similar patch some time ago, but it still
doesn't seem to be present in 2.4 or 2.6-test.

Andi: what about x86-64 - does it have something similar that should be
mentioned?


-- v --

v@iki.fi

--- linux/Documentation/nmi_watchdog.txt	Tue Sep 18 09:03:09 2001
+++ linux~/Documentation/nmi_watchdog.txt	Wed Jul 23 20:25:42 2003
@@ -8,9 +8,20 @@
 which get executed even if the system is otherwise locked up hard).
 This can be used to debug hard kernel lockups.  By executing periodic
 NMI interrupts, the kernel can monitor whether any CPU has locked up,
-and print out debugging messages if so.  You must enable the NMI
-watchdog at boot time with the 'nmi_watchdog=n' boot parameter.  Eg.
-the relevant lilo.conf entry:
+and print out debugging messages if so.  
+
+In order to use the NMI watchdoc, you need to have APIC support in your
+kernel. For SMP kernels, APIC support gets compiled in automatically. For
+UP, enable either CONFIG_X86_UP_APIC (Processor type and features -> Local
+APIC support on uniprocessors) or CONFIG_X86_UP_IOAPIC (Processor type and
+features -> IO-APIC support on uniprocessors) in your kernel config.
+CONFIG_X86_UP_APIC is for uniprocessor machines without an IO-APIC.
+CONFIG_X86_UP_IOAPIC is for uniprocessor with an IO-APIC. [Note: certain
+kernel debugging options, such as Kernel Stack Meter or Kernel Tracer,
+may implicitly disable the NMI watchdog.]
+
+To actually enable the NMI watchdog, use the 'nmi_watchdog=N' boot
+parameter.  Eg. the relevant lilo.conf entry:
 
         append="nmi_watchdog=1"
 

             reply	other threads:[~2003-07-23 17:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 17:43 Ville Herva [this message]
2003-07-28 17:53 ` [PATCH] NMI watchdog documentation Andi Kleen
2003-07-28 19:21   ` Ville Herva
2003-07-29 10:37 Mikael Pettersson
2003-07-29 16:06 ` Andi Kleen
2003-07-29 17:53   ` Ville Herva
2003-07-30 19:18 Mikael Pettersson
2003-07-30 19:20 Mikael Pettersson
2003-07-30 19:40 ` Ville Herva
2003-07-30 22:53 Mikael Pettersson
2003-07-31  5:44 ` Ville Herva
2003-07-31 21:25 Mikael Pettersson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030723174325.GL150921@niksula.cs.hut.fi \
    --to=vherva@niksula.hut.fi \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).