linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Svetoslav Slavtchev <svetljo@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Badness in kobject_get at lib/kobject.c:439
Date: Tue, 9 Dec 2003 15:28:29 -0800	[thread overview]
Message-ID: <20031209232829.GB1747@kroah.com> (raw)
In-Reply-To: <31715.1071010976@www51.gmx.net>

On Wed, Dec 10, 2003 at 12:02:56AM +0100, Svetoslav Slavtchev wrote:
> Call Trace:
>  [<c019a1f4>] kobject_get+0x30/0x3d
>  [<c01dd8d3>] class_get+0x1a/0x2c
>  [<c01ddb67>] class_device_add+0x41/0x110
>  [<c01cc4ec>] misc_add_class_device+0x63/0xc6
>  [<c01cc6d8>] misc_register+0xeb/0x120
>  [<c0361fd8>] apm_init+0x2ec/0x324

Hm, here's the problem.  Can you disable APM and see if the oops goes
away?  I bet apm_init() is being called before misc_init() is.

If you don't want to disable APM (and you should not have to) can you
apply the patch below to misc.c and let me know if it fixes your problem
or not?

thanks,

greg k-h

--- a/drivers/char/misc.c	Mon Oct  6 10:47:30 2003
+++ b/drivers/char/misc.c	Tue Dec  9 15:28:10 2003
@@ -407,4 +407,4 @@
 	}
 	return 0;
 }
-module_init(misc_init);
+subsys_initcall(misc_init);

  reply	other threads:[~2003-12-09 23:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 23:02 Badness in kobject_get at lib/kobject.c:439 Svetoslav Slavtchev
2003-12-09 23:28 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-10  0:36 Svetoslav Slavtchev
2003-12-10  0:41 ` Greg KH
2003-12-10  2:48   ` Svetoslav Slavtchev
2003-12-10  3:59   ` Svetoslav Slavtchev
2003-12-10 15:43     ` Greg KH
2003-12-09 20:46 Svetoslav Slavtchev
2003-12-09 13:51 Svetoslav Slavtchev
2003-12-09 20:19 ` Greg KH

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=20031209232829.GB1747@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=svetljo@gmx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).