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

Hi Don,

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

Thanks for the pointer. The 'd_real_path' function is part of
grsecurity, i'll see if they
can help :-)



      reply	other threads:[~2011-01-31 14:21 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
2011-01-31 14:21   ` Sebastian Färber [this message]

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 \
    --in-reply-to='' \ \ \ \
    --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).