public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Mikael Pettersson <mikpe@it.uu.se>, stable@kernel.org
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [BUG 2.6.29] NMI watchdog triggered in rb_insert_color called from enqueue_hrtimer
Date: Fri, 10 Apr 2009 15:10:51 +0200	[thread overview]
Message-ID: <20090410131051.GD31307@elte.hu> (raw)
In-Reply-To: <18909.58298.579959.482372@pilspetsen.it.uu.se>


* Mikael Pettersson <mikpe@it.uu.se> wrote:

> Mikael Pettersson writes:
>  > Ingo Molnar writes:
>  >  > 
>  >  > * Mikael Pettersson <mikpe@it.uu.se> wrote:
>  >  > 
>  >  > > Less than an hour after updating a dual Opteron 8384 box from 
>  >  > > 2.6.29-rc6 (which it had been running for weeks) to 2.6.29 final 
>  >  > > it died with the following watchdog-detected lockup:
>  >  > 
>  >  > Could you please check whether this is the bug fixed by:
>  >  > 
>  >  >   7f1e2ca: hrtimer: fix rq->lock inversion (again)
>  > 
>  > I am testing this now and will let you know how it goes.
> 
> The machine has now been running 2.6.29 plus that fix for more 
> than 24 hours with no problems. Previously it oopsed and hung 
> within an hour on two separate attempts to run 2.6.29 vanilla.

ok, thanks for testing. The fix is now upstream:

  7f1e2ca: hrtimer: fix rq->lock inversion (again)

-stable team, please pick it up - i just checked, it cherry-picks 
fine on v2.6.29.

	Ingo

      reply	other threads:[~2009-04-10 13:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  9:12 [BUG 2.6.29] NMI watchdog triggered in rb_insert_color called from enqueue_hrtimer Mikael Pettersson
2009-04-08  9:24 ` Ingo Molnar
2009-04-08  9:49   ` Peter Zijlstra
2009-04-08 11:29   ` Mikael Pettersson
2009-04-09 12:02     ` Mikael Pettersson
2009-04-10 13:10       ` Ingo Molnar [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:
  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=20090410131051.GD31307@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=stable@kernel.org \
    --cc=tglx@linutronix.de \
    /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