From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760412AbYA0XMu (ORCPT ); Sun, 27 Jan 2008 18:12:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754784AbYA0XMm (ORCPT ); Sun, 27 Jan 2008 18:12:42 -0500 Received: from py-out-1112.google.com ([64.233.166.178]:2303 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754732AbYA0XMl (ORCPT ); Sun, 27 Jan 2008 18:12:41 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type:content-transfer-encoding; b=lEPO54hvcUTglpne0PEOI1FyuhFnHlujS8GeRAN8JH4czu72SCZ0UYqSC3AfDzVnv7MIo2XBREsHNIznZHUHFaz2oAPqiaH0+jB0UZhuwCDS9hA0q713sPaStRSOrkCFFrEzUruMWgyQ7eBrchfiibG0HnYB20eVYvfRb7rS7i4= Date: Sun, 27 Jan 2008 19:12:38 -0400 From: Kevin Winchester To: Ingo Molnar Cc: Thomas Gleixner , "H. Peter Anvin" , Linux Kernel Mailing List , John Stultz Subject: Re: X fails to start with latest Linus git Message-Id: <20080127191238.92d95770.kjwinchester@gmail.com> In-Reply-To: <20080127124244.GA24999@elte.hu> References: <479BCE03.6070603@gmail.com> <479BD1D1.8020503@gmail.com> <20080127062703.GA23444@elte.hu> <20080127083129.c14452ca.kjwinchester@gmail.com> <20080127123702.GB21282@elte.hu> <20080127124120.GA23377@elte.hu> <20080127124244.GA24999@elte.hu> X-Mailer: Sylpheed 2.4.5 (GTK+ 2.12.0; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 27 Jan 2008 13:42:44 +0100 Ingo Molnar wrote: > > * Ingo Molnar wrote: > > > hm, perhaps it's due to the xtime lock dependency: > > > > do { > > seq = read_seqbegin(&xtime_lock); > > getnstimeofday(ts); > > tomono = wall_to_monotonic; > > > > } while (read_seqretry(&xtime_lock, seq)); > > > > perhaps your system somehow generates a printk from within an > > xtime_lock locked section? > > i _bet_ it's these printks that cause your lockup: > > [ 10.313437] Marking TSC unstable due to: cpufreq changes. > [ 10.313437] Time: hpet clocksource has been installed. > [ 10.424431] Clocksource tsc unstable (delta = -121609771 ns) > > as these are done with the xtime lock held. > Ok, I'll try disabling cpufreq to see if that prevents the lockup. If that is the problem, what is the fix? Just to keep the path reverted? -- Kevin Winchester