From: Daniel Walker <dwalker@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: bug: crash in adummy_init()
Date: Mon, 18 Dec 2006 08:40:31 -0800 [thread overview]
Message-ID: <1166460032.11560.9.camel@imap.mvista.com> (raw)
In-Reply-To: <20061218153145.GA17449@elte.hu>
On Mon, 2006-12-18 at 16:31 +0100, Ingo Molnar wrote:
> crash in adummy_init() - allyesconfig bootup.
>
> Ingo
>
> ---------------->
> Calling initcall 0xc1eb1f7e: adummy_init+0x0/0xb9()
> adummy: version 1.0
> swapper/1[CPU#0]: BUG in kref_get at lib/kref.c:32
> [<c0106273>] show_trace_log_lvl+0x34/0x4a
> [<c01063a9>] show_trace+0x2c/0x2e
> [<c01063d6>] dump_stack+0x2b/0x2d
> [<c0135acb>] __WARN_ON+0x63/0x75
> [<c04f0fb9>] kref_get+0x31/0x3c
> [<c04f028c>] kobject_get+0x1c/0x22
> [<c06e296a>] class_get+0x1d/0x2d
Here, adummy_init() depends on atm_init() and they're both in the same
initcall level. I wonder if there's suppose to be a set ordering inside
any given initcall level, I don't think there is.
Daniel
prev parent reply other threads:[~2006-12-18 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 15:31 bug: crash in adummy_init() Ingo Molnar
2006-12-18 16:40 ` Daniel Walker [this message]
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=1166460032.11560.9.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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