LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: [BUG] NMI watchdog lockups caused by mwait_idle
Date: Fri, 12 Jan 2007 16:24:44 -0800	[thread overview]
Message-ID: <EB12A50964762B4D8111D55B764A8454011D61F7@scsmsx413.amr.corp.intel.com> (raw)
In-Reply-To: <45A7F70E.80507@us.ibm.com>


Darrick,

I tried 2.6.20-rc4 on a Dempsey system here in my lab and it worked
fine. No watchdog lockups.
Can you try idle routine with hlt instead of mwait. There is no boot
option for this in x86_64, but you can change
arch/x86_64/kernel/process.c:select_idle_routine() not to enable mwait.
With that default kernel should use hlt based idle.

Also, worth seeing will be, what happens when nmi_watchdog=0,
nmi_watchdog=1, and nmi_watchdog=2 boot options. That should tell us
whether nmi_watchdog is raising some false alarm or the CPUs are indeed
getting locked up here..

Thanks,
Venki


>-----Original Message-----
>From: Darrick J. Wong [mailto:djwong@us.ibm.com] 
>Sent: Friday, January 12, 2007 1:01 PM
>To: Pallipadi, Venkatesh
>Cc: Linux Kernel Mailing List
>Subject: [BUG] NMI watchdog lockups caused by mwait_idle
>
>Hi Venkatesh,
>
>I have an IBM IntelliStation Z30 with two Dempsey CPUs.  When I try to
>boot 2.6.20-rc4 on it, the system prints messages about NMI watchdog
>lockups.  git-bisect determined that the patch "[PATCH] x86-64: Fix
>interrupt race in idle callback (3rd try)" was the source of these
>problems, and I can work around the problem either by passing
>"idle=poll" to get avoid mwait_idle or by reverting the patch.
>
>Other non-Dempsey Xeon machines with mwait support do not exhibit these
>symptoms.  I will try to determine if this is a bug specific to Dempsey
>CPUs or this particular type of machine.  I suspect the latter, but I
>don't know enough about monitor/mwait to pursue this much further.
>
>What else can I do to diagnose this?
>
>--D
>

  reply	other threads:[~2007-01-13  0:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 21:01 Darrick J. Wong
2007-01-13  0:24 ` Pallipadi, Venkatesh [this message]
2007-01-13  0:46   ` Darrick J. Wong

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=EB12A50964762B4D8111D55B764A8454011D61F7@scsmsx413.amr.corp.intel.com \
    --to=venkatesh.pallipadi@intel.com \
    --cc=djwong@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='RE: [BUG] NMI watchdog lockups caused by mwait_idle' \
    /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

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).