All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Diffie <diffie@blazebox.homeip.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Badness in device_release at drivers/base/core.c:84
Date: Fri, 1 Aug 2003 14:27:50 -0700	[thread overview]
Message-ID: <20030801212750.GB31881@kroah.com> (raw)
In-Reply-To: <20030801182207.GA3759@blazebox.homeip.net>

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.

thanks,

greg k-h

  reply	other threads:[~2003-08-01 21:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 18:22 Badness in device_release at drivers/base/core.c:84 Diffie
2003-08-01 21:27 ` Greg KH [this message]
2003-08-02  5:40   ` Diffie
2003-08-01 21:44 ` Andrew Morton
2003-08-01 23:27   ` Mike Anderson
2003-08-02  5:57     ` Diffie
2003-08-02  5:53   ` Diffie
2003-08-03  1:55   ` Diffie
2003-08-03  2:07     ` Andrew Morton
2003-08-03 21:47       ` Diffie
2003-08-03 21:52         ` Andrew Morton
2003-08-03 22:23           ` Diffie
2003-08-03 22:31             ` Diffie
2003-08-04 16:30               ` Patrick Mansfield
2003-08-04 17:48                 ` Paul Blazejowski
2003-08-04 18:26                 ` Paul Blazejowski
2003-08-04 18:57                   ` Patrick Mansfield
2003-08-04 19:36                   ` Justin T. Gibbs
2003-08-05  2:21                     ` Paul Blazejowski
2003-08-05 10:20                       ` wb
2003-08-05 16:10                         ` Ishikawa
2003-08-06 16:58                           ` Paul Blazejowski
2003-08-06 17:20                             ` Chiaki
2003-08-13  2:03                               ` Chiaki
2003-08-06 16:55                         ` Paul Blazejowski
2003-08-05  7:18                     ` Paul Blazejowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030801212750.GB31881@kroah.com \
    --to=greg@kroah.com \
    --cc=diffie@blazebox.homeip.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.