From: Greg KH <gregkh@linuxfoundation.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kobject (ffff88003ffbb4b8): tried to init an initialized object, something is seriously wrong.
Date: Mon, 6 Feb 2012 10:29:56 -0800 [thread overview]
Message-ID: <20120206182956.GA13819@kroah.com> (raw)
In-Reply-To: <20120206182040.GA1862@phenom.dumpdata.com>
On Mon, Feb 06, 2012 at 01:20:40PM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Feb 03, 2012 at 01:42:35PM -0800, Greg KH wrote:
> > On Fri, Feb 03, 2012 at 01:39:49PM -0800, Greg KH wrote:
> > > On Fri, Feb 03, 2012 at 03:59:53PM -0500, Konrad Rzeszutek Wilk wrote:
> > > > 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.
> > >
> > > No, it's related to the previous issue, let me knock up a patch to fix
> > > this as well...
> >
> > Does this patch solve the problem for you?
>
> Yeah, no warnings. But neither is the CPU coming back up :-(
Very wierd.
> Thought that might be related to something else - let me double check
> with 3.2 whether there are some race-conditions that I might be hitting.
Ok, I'll wait to queue this up until you get back to me.
greg k-h
next prev parent reply other threads:[~2012-02-06 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 20:59 kobject (ffff88003ffbb4b8): tried to init an initialized object, something is seriously wrong Konrad Rzeszutek Wilk
2012-02-03 21:39 ` Greg KH
2012-02-03 21:42 ` Greg KH
2012-02-06 18:20 ` Konrad Rzeszutek Wilk
2012-02-06 18:29 ` Greg KH [this message]
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=20120206182956.GA13819@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox