From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 14DF7DDDF5 for ; Thu, 24 Jan 2008 19:46:46 +1100 (EST) Subject: Re: ppc32: Weird process scheduling behaviour with 2.6.24-rc From: Benjamin Herrenschmidt To: Peter Zijlstra In-Reply-To: <1201091798.6341.49.camel@lappy> References: <1200659696.23161.81.camel@thor.sulgenrain.local> <1201013786.4726.28.camel@thor.sulgenrain.local> <1201090699.9052.39.camel@thor.sulgenrain.local> <1201091798.6341.49.camel@lappy> Content-Type: text/plain Date: Thu, 24 Jan 2008 19:46:12 +1100 Message-Id: <1201164372.6815.55.camel@pasglop> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org, Ingo Molnar , Michel =?ISO-8859-1?Q?D=E4nzer?= Reply-To: benh@kernel.crashing.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Could the fact that our sched_clock() returns utter crap if called before time_init() explain the problem ? If yes, that's an easy fix. Ben.