[lkml]   [2003]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Badness in device_release at drivers/base/core.c:84
On Fri, Aug 01, 2003 at 02:22:07PM -0400, Diffie wrote:
> Under 2.6.0-test2-mm2 keeps getting Badness in device_release at
> drivers/base/core.c:84 when loading USB modules on NFORCE2 based board.
> uname: Linux blaze 2.6.0-test2-mm2 #1 Thu Jul 31 13:11:05 EDT 2003 i686
> unknown on Linux Slackware 9.0, GCC 3.2.2
> Device '' does not have a release() function, it is broken and must be
> fixed.
> Badness in device_release at drivers/base/core.c:84
> Call Trace:
> [<c021dfd8>] kobject_cleanup+0x88/0x90
> [<c02c03ff>] hub_port_connect_change+0x2af/0x330
> [<c02bfcfd>] hub_port_status+0x3d/0xb0
> [<c02c07bd>] hub_events+0x33d/0x3b0
> [<c02c0865>] hub_thread+0x35/0xf0
> [<c011b810>] default_wake_function+0x0/0x30
> [<c02c0830>] hub_thread+0x0/0xf0
> [<c01070c9>] kernel_thread_helper+0x5/0xc

The USB warnings should all be fixed up with the patches I just sent to
Linus, so you can safely ignore them for now.

As for the oops, I have no idea, sorry.


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:47    [W:0.104 / U:0.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site