mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andi Kleen <andi@firstfloor.org>
Cc: Greg KH <greg@kroah.com>,
	"Langsdorf, Mark" <mark.langsdorf@amd.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Warning in during hotplug on 2.6.27-rc2-git5
Date: Sun, 17 Aug 2008 21:23:18 +0200	[thread overview]
Message-ID: <200808172123.19172.rjw@sisk.pl> (raw)
In-Reply-To: <200808171925.48584.rjw@sisk.pl>

On Sunday, 17 of August 2008, Rafael J. Wysocki wrote:
> On Sunday, 17 of August 2008, Andi Kleen wrote:
> > > > > I'm still seeing it on 2.6.27-rc2, even with the 
> > > > > patch here http://lkml.org/lkml/2008/7/30/171 and the
> > > > > wbinvd_halt code patch applied.  Maybe something else
> > > > > broke in some of the recent hotplug changes?
> > > > 
> > > > My guess is that MCE does somthing that is not allowed by sysfs any more.
> > > 
> > > Hm, sysfs hasn't changed any in 2.6.27-rcX that I know of.
> > 
> > mce hasn't either in this regard. My current theory is that the CPU 
> > up/down notifiers are not balanced anymore (as in duplicated up events) 
> 
> It doesn't look like this is the case.  Moreover, had that been the case, we'd
> have had many reports from people doing suspend/hibernation, but it doesn't
> happen.
> 
> I think that cpu_down() fails for some reason and that causes the subsequent
> onlining to fail.

Well, no.  If my understanding of the CPU hotplug code is correct, this is not
possible.

The next possibility is that for some 'i' mce_attributes[i] is NULL, although
there are non-NULL values for some j > i.  In that case, mce_remove_device()
would fail to remove device_mce for given CPU and the subsequent
mce_create_device() would cause the observed failure.

Thanks,
Rafael

  reply	other threads:[~2008-08-17 19:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 22:00 Mark Langsdorf
2008-08-14 15:53 ` Rafael J. Wysocki
2008-08-14 16:06   ` Langsdorf, Mark
2008-08-14 16:34   ` Andi Kleen
2008-08-14 18:35     ` Langsdorf, Mark
2008-08-16 19:28       ` Rafael J. Wysocki
2008-08-16 20:18         ` Greg KH
2008-08-16 21:34           ` Rafael J. Wysocki
2008-08-18 15:32             ` Langsdorf, Mark
2008-08-17  2:23           ` Andi Kleen
2008-08-17 17:25             ` Rafael J. Wysocki
2008-08-17 19:23               ` Rafael J. Wysocki [this message]
2008-08-17  2:25       ` Andi Kleen
2008-08-17 21:53       ` Rafael J. Wysocki
2008-08-18 13:11         ` Langsdorf, Mark
2008-08-18 14:38           ` Rafael J. Wysocki
2008-08-18 16:29             ` Langsdorf, Mark
2008-08-18 16:42               ` Rafael J. Wysocki

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=200808172123.19172.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.langsdorf@amd.com \
    --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

all inboxes | Powered by JetHome®