Messages in this thread | | | Date | Fri, 6 Feb 2004 09:47:30 -0500 | From | Ben Collins <> | Subject | Re: 2.6.2-mm1 aka "Geriatric Wombat" |
| |
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: > > [<c0239966>] kobject_get+0x36/0x40 > > [<c027cc73>] get_device+0x13/0x20 > > [<c027d899>] bus_for_each_dev+0x59/0xc0 > > [<d0939355>] nodemgr_node_probe+0x55/0x120 [ieee1394] > > [<d0939200>] nodemgr_probe_ne_cb+0x0/0x90 [ieee1394] > > [<d0939748>] nodemgr_host_thread+0x168/0x190 [ieee1394] > > [<d09395e0>] nodemgr_host_thread+0x0/0x190 [ieee1394] > > [<c010ac15>] 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/ - 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/
| |