LKML Archive on
help / color / mirror / Atom feed
From: Don Zickus <>
To: "Sebastian Färber" <>
Subject: Re: Hard LOCKUP with (maybe scheduler/tick related?)
Date: Mon, 31 Jan 2011 08:52:18 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Jan 31, 2011 at 12:05:58PM +0100, Sebastian Färber wrote:
> Hi,
> i recently upgraded some servers from to and see
> frequent "hard lockups" on
> a few of them now. I've compiled a kernel with debugging support and
> enabled the "NMI Watchdog"
> to get more information.
> I've attached my .config and the stack traces from the nmi watchdog,
> captured via a serial console.
> To me it looks like there is some problem in run_posix_cpu_timers and
> the problem is also
> triggering WARNING: at kernel/sched_fair.c:979 hrtick_start_fair.
> Note that the kernel is patched with grsecurity and i'm running CONFIG_NO_HZ.
> There were no problems with
> Would be great if someone could have a look at this, i can provide
> more information if neccessary.

Your attached 'crash' details had another stacktrace first.  That one
shows the nmi_watchdog triggering because a spin_lock is spinning forever
in 'd_real_path'.  I couldn't find that code in any upstream tree, then
again I was too lazy to clone the stable trees.  So I don't know what the
exact problem is, but if you look through the git history of and
revert things that relate to 'd_real_path', you can probably workaround
the problem for now, until someone who knows that stuff better than me can
give you a better answer.


  reply	other threads:[~2011-01-31 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 11:05 Sebastian Färber
2011-01-31 13:52 ` Don Zickus [this message]
2011-01-31 14:21   ` Sebastian Färber

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:

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

  git send-email \ \ \ \ \
    --subject='Re: Hard LOCKUP with (maybe scheduler/tick related?)' \

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