From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758678AbZHRKtK (ORCPT ); Tue, 18 Aug 2009 06:49:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758668AbZHRKtJ (ORCPT ); Tue, 18 Aug 2009 06:49:09 -0400 Received: from mail-bw0-f222.google.com ([209.85.218.222]:46649 "EHLO mail-bw0-f222.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758544AbZHRKtH (ORCPT ); Tue, 18 Aug 2009 06:49:07 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=p4mw9MpGdknVxNVIgdOAPHjkmmag6kB82Q1jhrnb6KcxBsFd8VoJD92EgUtVl1zRPe zUpz57TnTlKfJRx/Ktn3bG83ny4/cPkHKcd7Y+ECIf2r5ueyqCBSr/ZykFoEy8ueyqj3 ZTbzQn9erxs2o915eNylTU9Gdw6iqLSy3xGxw= Date: Tue, 18 Aug 2009 12:49:06 +0200 From: Frederic Weisbecker To: "Justin P. Mattock" Cc: Linux Kernel Mailing List Subject: Re: system gets stuck in a lock during boot Message-ID: <20090818104905.GC5231@nowhere> References: <4A84345D.60506@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A84345D.60506@gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 13, 2009 at 08:42:21AM -0700, Justin P. Mattock wrote: > I posted already and had no reply, > I cannot boot my system with the latest git > > seems to be stuck in some lock: > > [ 0.655640] [] panic+0x84/0x129 > [ 0.655883] [] do_exit+0x84/0x67e > [ 0.656125] [] oops_end+0x9c/0xb7 > [ 0.656368] [] no_context+0x200/0x223 > [ 0.656611] [] ? __mutex_lock_slowpath+0x226/0x249 > [ 0.656848] [] __bad_area_nosemaphore+0x1a7/0x1e1 > [ 0.657097] []? mutex_unlock+0x1c/0x32 > [ 0.657097] [] ? inode_doinit_with_dentry+0x533/0x5be > [ 0.657579] [] ? _spin_unlock+0x1c/0x32 > [ 0.657822] [] bad_area_nosemaphore+0x2a/0x40 > [ 0.658066] [] ? selinux_d_instantiate+0x2a/0x40 > [ 0.658309] [] do_page_fault+0x192/0x2dd > [ 0.658549] [] page_fault+0x1f/0x30 > [ 0.658791] [] ? strcmp+0x17/0x46 > [ 0.659040] [] event_create_dir+0x49/0x37b Ouch... I've never seen such panic. Could you send me your config, hopefully I could reproduce it? Thanks. > [ 0.659276] [] ? event_trace_init+0x0/0x1a2 > [ 0.659519] [] event_trace_init+0x157/0x1a2 > [ 0.659762] [] ? event_trace_init+0x0/0x1a2 > [ 0.660008] [] do_one_initcall+0x65/0x14e > [ 0.660251] [] ? proc_set_super+0x49/0x5d > [ 0.660488] [] kernel_init+0x160/0x1cc > [ 0.660731] [] child_rip+0xa/0x20 > [ 0.660973] [] ? kernel_init+0x0/0x1cc > [ 0.661220] [] ? child_rip+0x0/0x20 > > > > seems my other machine boots just fine, maybe this is something > with x86_64. > > Justin P. Mattock > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/