Messages in this thread | | | Date | Sat, 7 Feb 2004 11:13:15 -0800 | From | Greg KH <> | Subject | Re: 2.6.2-mm1 aka "Geriatric Wombat" |
| |
On Sat, Feb 07, 2004 at 12:27:58PM -0500, Ben Collins wrote: > On Fri, Feb 06, 2004 at 10:22:00AM -0800, Greg KH wrote: > > On Fri, Feb 06, 2004 at 09:47:30AM -0500, Ben Collins wrote: > > > 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()? > > > > No, not at all. You are initializing the structure to 0 before setting > > any fields in it, right? But that wouldn't be the symptom we are seeing > > here... > > Yeah, it's being memset() to zero. After that I set the parent and the > bus_id, and then call device_register(). > > One thing I notice is that I am not checking the return value of > device_register(), however if that fails, the device shouldn't be in the > device list for the bus, correct?
That is correct. I don't see the problem either in looking at your code...
thanks,
greg k-h - 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/
| |