From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: kobject (ffff88003ffbb4b8): tried to init an initialized object, something is seriously wrong.
Date: Fri, 3 Feb 2012 15:59:53 -0500 [thread overview]
Message-ID: <20120203205953.GA2897@phenom.dumpdata.com> (raw)
Hey Greg,
With or without your previous patch (the one that added an cpu_device_release
function) I am getting this in 3.3-rc2. I did not get this in 3.2.
I added some extra printks to make sure that the handle_vcpu_hotplug_event
code actually did call 'arch_unregister_cpu' which is certainly looks
to be doing.
I hadn't done a bisection yet, but was wondering if this is related
to the previous issues with the sysdev. Or kobject getting more observant.
[ 34.984105] Disabling CPU3 present
[ 34.984801] arch_unregister_cpu: CPU 3
sh-4.1#
sh-4.1#
sh-4.1# [ 42.297542] Contemplating CPU 0 which should be online
[ 42.298447] Enabling CPU0 present online
[ 42.299229] Contemplating CPU 1 which should be online
[ 42.300001] Enabling CPU1 present online
[ 42.300783] Contemplating CPU 2 which should be online
[ 42.301558] Enabling CPU2 present online
[ 42.302387] Contemplating CPU 3 which should be online
[ 42.303198] Enabling CPU3
[ 42.303895] arch_register_cpu: CPU 3
[ 42.304188] kobject (ffff88003ffbb4b8): tried to init an initialized object, something is seriously wrong.
[ 42.304188] Pid: 30, comm: xenwatch Tainted: G O 3.3.0-rc2-00008-g4b64969 #1
[ 42.304188] Call Trace:
[ 42.304188] [<ffffffff812ce4d9>] kobject_init+0x89/0xa0
[ 42.304188] [<ffffffff813ca917>] device_initialize+0x27/0x90
[ 42.304188] [<ffffffff813cbbc1>] device_register+0x11/0x20
[ 42.304188] [<ffffffff815f2210>] register_cpu+0x52/0xb6
[ 42.304188] [<ffffffff815d66c0>] arch_register_cpu+0x60/0x70
[ 42.304188] [<ffffffff8136b095>] handle_vcpu_hotplug_event+0x175/0x180
[ 42.304188] [<ffffffff81367140>] xenwatch_thread+0xb0/0x180
[ 42.304188] [<ffffffff810a7ec0>] ? wake_up_bit+0x40/0x40
[ 42.304188] [<ffffffff81367090>] ? split+0xf0/0xf0
[ 42.304188] [<ffffffff810a77e6>] kthread+0x96/0xa0
[ 42.304188] [<ffffffff815fec24>] kernel_thread_helper+0x4/0x10
[ 42.304188] [<ffffffff815f6b40>] ? retint_restore_args+0x5/0x6
[ 42.304188] [<ffffffff815fec20>] ? gs_change+0x13/0x13
next reply other threads:[~2012-02-03 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 20:59 Konrad Rzeszutek Wilk [this message]
2012-02-03 21:39 ` kobject (ffff88003ffbb4b8): tried to init an initialized object, something is seriously wrong Greg KH
2012-02-03 21:42 ` Greg KH
2012-02-06 18:20 ` Konrad Rzeszutek Wilk
2012-02-06 18:29 ` Greg KH
2012-02-08 0:35 ` Konrad Rzeszutek Wilk
2012-02-08 1:34 ` 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=20120203205953.GA2897@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=gregkh@linuxfoundation.org \
--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.