From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265470AbUBFOs7 (ORCPT ); Fri, 6 Feb 2004 09:48:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265473AbUBFOs7 (ORCPT ); Fri, 6 Feb 2004 09:48:59 -0500 Received: from bristol.phunnypharm.org ([65.207.35.130]:58344 "EHLO bristol.phunnypharm.org") by vger.kernel.org with ESMTP id S265470AbUBFOs5 (ORCPT ); Fri, 6 Feb 2004 09:48:57 -0500 Date: Fri, 6 Feb 2004 09:47:30 -0500 From: Ben Collins To: Greg KH Cc: Robert Gadsdon , Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: 2.6.2-mm1 aka "Geriatric Wombat" Message-ID: <20040206144729.GJ1042@phunnypharm.org> References: <402240F9.3050607@gadsdon.giointernet.co.uk> <20040205182614.GG13075@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040205182614.GG13075@kroah.com> User-Agent: Mutt/1.5.5.1+cvs20040105i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 05, 2004 at 10:26:14AM -0800, Greg KH wrote: > On Thu, Feb 05, 2004 at 01:11:21PM +0000, Robert Gadsdon wrote: > > 2.6.2-mm1 tombstone "Badness in kobject_get....." when booting: > > Oooh, not nice. That means a kobject is being used before it has been > initialized. Glad to see that check finally helps out... Doesn't sound like a bug in ieee1394. This bus for each is done on the ieee1394_bus_type, which is registered way ahead of time. Nothing is in that device list that didn't come from device_register(). Has something new changed to where I need to prep the device more before passing it to device_register()? > > ieee1394: Host added: ID:BUS[0-00:1023] GUID[090050c50000046f] > > Badness in kobject_get at lib/kobject.c:431 > > Call Trace: > > [] kobject_get+0x36/0x40 > > [] get_device+0x13/0x20 > > [] bus_for_each_dev+0x59/0xc0 > > [] nodemgr_node_probe+0x55/0x120 [ieee1394] > > [] nodemgr_probe_ne_cb+0x0/0x90 [ieee1394] > > [] nodemgr_host_thread+0x168/0x190 [ieee1394] > > [] nodemgr_host_thread+0x0/0x190 [ieee1394] > > [] kernel_thread_helper+0x5/0x10 > > Looks like one of the ieee1394 patches causes this. Ben? > > thanks, > > greg k-h -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/