mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Mark Haverkamp <markh@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	lse-tech <lse-tech@lists.sourceforge.net>
Subject: Re: 2.5.62-mjb3 (scalability / NUMA patchset)
Date: Wed, 26 Feb 2003 15:05:08 -0800	[thread overview]
Message-ID: <4790000.1046300707@[10.10.2.4]> (raw)
In-Reply-To: <1046300601.3375.13.camel@markh1.pdx.osdl.net>

>> > I turned on NMI watchdogs and when the system hung, I saw no output.
>> > My serial console is through a terminal server that isn't set up to
>> > pass along the sysrq, so I need to get this fixed.  In any case I
>> > backed out the patch that you suggested and I have had no system hangs
>> > since.
>> 
>> OK, I'll back out that patch for now, but it seems to indicate underlying
>> crud. What parameter did you set for NMI watchdog?
> 
> I set it to 1. In Documentation/nmi_watchdog.txt this looked like the
> only option.  Now that I look at apic.h, I see that I could set it to 2
> also. If you like I can try this also.

2 is what we used sucessfully last time, but I can't remember the
difference off the top of my head ... if you could try that, would be most
useful.

M.


  reply	other threads:[~2003-02-26 22:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6490000.1045713212@[10.10.2.4]>
2003-02-24 18:08 ` Martin J. Bligh
2003-02-26 15:36   ` Mark Haverkamp
2003-02-26 15:55     ` Martin J. Bligh
2003-02-26 16:03       ` Mark Haverkamp
2003-02-26 22:49       ` Mark Haverkamp
2003-02-26 22:51         ` Randy.Dunlap
2003-02-26 22:53         ` Martin J. Bligh
2003-02-26 23:03           ` Mark Haverkamp
2003-02-26 23:05             ` Martin J. Bligh [this message]
2003-02-27 17:22               ` Mark Haverkamp

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='4790000.1046300707@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=markh@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

all inboxes | Powered by JetHome®