mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "the arch/x86 maintainers" <x86@kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: latest -git: WARNING: at arch/x86/kernel/ipi.c:123 send_IPI_mask_bitmask+0xc3/0xe0()
Date: Wed, 20 Aug 2008 08:26:19 +0200	[thread overview]
Message-ID: <19f34abd0808192326jc10e758m99e76bbd5714c5b8@mail.gmail.com> (raw)
In-Reply-To: <20080820013930.GN9807@one.firstfloor.org>

On Wed, Aug 20, 2008 at 3:39 AM, Andi Kleen <andi@firstfloor.org> wrote:
> On Tue, Aug 19, 2008 at 09:51:44PM +0200, Vegard Nossum wrote:
>> Hi,
>>
>> With latest -git (1fca25427482387689fa27594c992a961d98768f), I got
>> this on reading from /dev/cpu/*/* while hot-unplugging cpu1.
>
> It's generally known the oprofile doesn't support CPU hotplug well.
> Someone needs to make a project out of fixing it properly. Right now
> it's just a "don't do that when it hurts"

Hm. What you say is true, but this one in particular has nothing to do
with oprofile! It has something to do with reading /dev/cpu/*/msr
while hot-unplugging cpu1:

 [<c011733e>] msr_read+0x6e/0xa0
 [<c01a87b4>] vfs_read+0x94/0x130

I wasn't using oprofile when this happened. So I think it should also
be considered a separate issue. Though yes -- CPU hotplug in general
tends to break a lot of things.


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

  reply	other threads:[~2008-08-20  6:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 19:51 Vegard Nossum
2008-08-20  1:39 ` Andi Kleen
2008-08-20  6:26   ` Vegard Nossum [this message]
2008-08-22  0:36     ` Dave Jones
2008-08-22  2:13       ` H. Peter Anvin
2008-08-22  2:28         ` Andi Kleen
2008-08-22  6:24           ` H. Peter Anvin
2008-08-22  9:35             ` Andi Kleen
2008-08-22 16:41               ` H. Peter Anvin
2008-08-23  6:42                 ` Jeremy Fitzhardinge
2008-08-23  6:44                   ` H. Peter Anvin
2008-08-22 11:13           ` adobriyan
2008-08-24  9:20         ` Vegard Nossum
2008-08-24 16:43           ` H. Peter Anvin
2008-08-24 17:17           ` H. Peter Anvin
2008-08-24 17:22             ` Vegard Nossum
2008-08-24 17:45               ` Vegard Nossum
2008-08-24 17:59                 ` H. Peter Anvin
2008-08-24 18:13                 ` Dave Jones
2008-08-25 18:31                   ` Vegard Nossum
2008-08-25 18:38                     ` Dave Jones
2008-08-25 18:36                   ` Andi Kleen
2008-08-25 18:54                     ` Dave Jones
2008-08-25 19:39                       ` Andi Kleen
2008-08-25 19:50                         ` Dave Jones
2008-08-25 20:36                           ` Andi Kleen
2008-08-25 20:47                             ` Dave Jones
2008-08-25 21:24                               ` Arjan van de Ven
2008-08-25 19:08                     ` H. Peter Anvin
2008-08-25 19:13                       ` Dave Jones

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=19f34abd0808192326jc10e758m99e76bbd5714c5b8@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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

all inboxes | Powered by JetHome®