linux-kernel - Re: [GIT PULL rcu/next] rcu commits for 2.6.40

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110512092013.GJ2258@linux.vnet.ibm.com>
Date:	Thu, 12 May 2011 02:20:13 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL rcu/next] rcu commits for 2.6.40

On Thu, May 12, 2011 at 12:42:50AM -0700, Yinghai Lu wrote:
> On 05/12/2011 12:27 AM, Yinghai Lu wrote:
> > On 05/11/2011 11:03 PM, Ingo Molnar wrote:
> >>
> >> * Yinghai Lu <yinghai@...nel.org> wrote:
> >>
> >>> e59fb3120becfb36b22ddb8bd27d065d3cdca499 is the first bad commit
> >>> commit e59fb3120becfb36b22ddb8bd27d065d3cdca499
> >>> Author: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> >>> Date:   Tue Sep 7 10:38:22 2010 -0700
> >>>
> >>>     rcu: Decrease memory-barrier usage based on semi-formal proof
> >>
> >> Find below an (untested!) attempt at reverting it for debugging purposes: could 
> >> you please try it, does your system now boot up fine?
> >>
> >> Thanks,
> >>
> >> 	Ingo
> >>
> > 
> > yes, reverted manually that commit fix the problem.
> 
> on system with 8 sockets westmere-ex
> 
> it seems other commits after that commit contribute some delay too.
> 
> [   32.240739] cpu_dev_init done
> [   73.587288] memory_dev_init done

I am testing a revert of e59fb3120becfb36b22ddb8bd27d065d3cdca499 and
will chase down the delay.

Could you please send along your .config file?

							Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/