From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764356AbYBTXgR (ORCPT ); Wed, 20 Feb 2008 18:36:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754674AbYBTXgB (ORCPT ); Wed, 20 Feb 2008 18:36:01 -0500 Received: from sj-iport-3.cisco.com ([171.71.176.72]:6129 "EHLO sj-iport-3.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752153AbYBTXgA (ORCPT ); Wed, 20 Feb 2008 18:36:00 -0500 To: "Tony Luck" Cc: "David Miller" , mingo@elte.hu, linux-kernel@vger.kernel.org Subject: Re: Strange hang on ia64 with CONFIG_PRINTK_TIME=y X-Message-Flag: Warning: May contain useful information References: <20080213125725.GC6344@elte.hu> <20080213.050340.64342037.davem@davemloft.net> <12c511ca0802131659u6e4407d9w96148fe72d6e11d7@mail.gmail.com> <20080213.170452.68851396.davem@davemloft.net> <12c511ca0802131933g6aaaec9cidbfbfcac6f394c63@mail.gmail.com> <12c511ca0802141327j6e31e8c2tee1d679053b604fc@mail.gmail.com> <1FE6DD409037234FAB833C420AA843EC97C8B0@orsmsx424.amr.corp.intel.com> <12c511ca0802141817i3295e83cxd7c05e07f2c54fea@mail.gmail.com> <12c511ca0802191440q6a2f5604xe6b563c32c3a90b2@mail.gmail.com> From: Roland Dreier Date: Wed, 20 Feb 2008 15:35:58 -0800 In-Reply-To: <12c511ca0802191440q6a2f5604xe6b563c32c3a90b2@mail.gmail.com> (Tony Luck's message of "Tue, 19 Feb 2008 14:40:35 -0800") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.21 (linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-OriginalArrivalTime: 20 Feb 2008 23:35:58.0611 (UTC) FILETIME=[58657E30:01C87419] Authentication-Results: sj-dkim-2; header.From=rdreier@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > I just tried Ingo's patch[1] on a 2.6.25-rc2 kernel with printk timestamps > turned on ... and it booted just fine on my tiger4. The default path > for non-boot cpus is from head.S to start_secondary(), and that > calls cpu_init() pretty quickly. There shouldn't normally[2] be any > printk() calls on the non-boot cpu before it is safe to do so. Hmm, current git + Ingo's patch still hangs on boot on my system ("Hitachi Cold Fusion-3e 2S4U" according to DMI). - R.