mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Martin Schwidefsky <schwidefsky@googlemail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Valdis.Kletnieks@vt.edu,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: 2.6.32-rc5-mmotm1101 - lockdep whinge during early boot
Date: Mon, 9 Nov 2009 10:43:09 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911091038010.2725@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0911051748090.12138@localhost.localdomain>

On Thu, 5 Nov 2009, Thomas Gleixner wrote:
> On Thu, 5 Nov 2009, Martin Schwidefsky wrote:
> > >
> > > Which basically reverts commit 7285dd7fd375763bfb8ab1ac9cf3f1206f503c16
> > >
> > 
> > It is this commit in linux-next:
> > 
> > commit 66b1a72ceaa7da811db025855f19482f0a38e815
> > Author: Ingo Molnar <mingo@elte.hu>
> > Date:   Thu Sep 10 19:39:52 2009 +0200
> > 
> >     Revert "clocksource: Resolve cpu hotplug dead lock with TSC unstable"
> > 
> >     This reverts commit 7285dd7fd375763bfb8ab1ac9cf3f1206f503c16.
> > 
> >     causes crashes.
> > 
> >     Signed-off-by: Ingo Molnar <mingo@elte.hu>
> 
> Eeek. We fixed this in mainline via:
> 
> commit f79e0258ea1f04d63db499479b5fb855dff6dbc5
> Author: Martin Schwidefsky <schwidefsky@de.ibm.com>
> Date:   Fri Sep 11 15:33:05 2009 +0200
> 
>     clocksource: Resolve cpu hotplug dead lock with TSC unstable, fix crash
> 
> and
> 
> commit 54a6bc0b071c50150bc6d1da16c2cd9a963e288c
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date:   Mon Sep 14 19:49:02 2009 +0200
> 
>     clocksource: Delay clocksource down rating to late boot
> 
> 
> These patches came via the tip tree right at the beginning of the
> merge window several days _before_ I asked Linus to pull the timer
> code for 32.
> 
> So there is something weird going on.

Ok, figured out what happened.

The revert has been in next via the tip-tree for some days when
testing turned up the problem and the fixes were not ready.

So it looks like Andrew picked exactly such a linux-next snapshot to
create his baseline patch.

linux-next, tip, mainline of today all have the correct and functional
code.

Thanks,

	tglx

      reply	other threads:[~2009-11-09  9:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 16:11 Valdis.Kletnieks
2009-11-05  9:11 ` Rusty Russell
2009-11-05 14:10   ` Oleg Nesterov
2009-11-05 14:54     ` Martin Schwidefsky
2009-11-05 14:54     ` Thomas Gleixner
2009-11-05 15:22       ` Oleg Nesterov
2009-11-05 15:33         ` Oleg Nesterov
2009-11-05 15:54           ` Thomas Gleixner
2009-11-05 16:20             ` Martin Schwidefsky
2009-11-05 16:53               ` Thomas Gleixner
2009-11-09  9:43                 ` Thomas Gleixner [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=alpine.LFD.2.00.0911091038010.2725@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=schwidefsky@googlemail.com \
    /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®