From: Tomas Carnecky <tom@dbservice.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, lenb@kernel.org
Subject: Re: WARNING: smp_call_function_single() and smp_call_function_mask()
Date: Mon, 03 Dec 2007 21:13:57 +0100 [thread overview]
Message-ID: <47546385.1010708@dbservice.com> (raw)
In-Reply-To: <20071201084833.63263489@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Sun, 02 Dec 2007 09:43:39 +0100
> Tomas Carnecky <tom@dbservice.com> wrote:
>
>> WARNING: at arch/x86/kernel/smp_64.c:427 smp_call_function_single()
>> WARNING: at arch/x86/kernel/smp_64.c:397 smp_call_function_mask()
>>
>> dmesg and config attached.
>>
>> I'm getting about three of each at boot. I'm running:
>> commit e1cca7e8d484390169777b423a7fe46c7021fec1
>> Date: Thu Nov 29 16:25:29 2007 -0800
>> which is the latest git as of yesterday plus a one (unrelated) debug
>> statement patch in usb uhci.
>>
>> There was a similar bug report after 2.6.23-rc8-mm was released.
>> Though there seems to be a fundamental problem with how people use
>> smp_call_function*() [1]. And this can just as well be another
>> incarnation of it.
>>
>> Is that easy enough to fix or do I need to bisect (it didn't happen in
>> 2.6.24-rc3)?
>>
>
> this appears to be a bug in the acpi code, to be exact in
> processor_throttling.c file, function
> acpi_processor_set_throttling_ptc(); it disables interrupts and then
> appears to do a cross-cpu IPI to set the state. Well... we can't do
> that due to deadlock reasons (you can't do IPI's with interrupts off or
> you can get a very nice deadlock with the cpu that you IPI trying to
> do the same thing to you).
>
I updated the kernel today (to 1a2edea9aff48...) and the warnings are gone.
tom
next prev parent reply other threads:[~2007-12-03 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 8:43 WARNING: smp_call_function_single() and smp_call_function_mask() Tomas Carnecky
2007-12-01 16:48 ` Arjan van de Ven
2007-12-03 20:13 ` Tomas Carnecky [this message]
2007-12-03 20:46 ` Pallipadi, Venkatesh
2007-12-02 8:49 ` Tomas Carnecky
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=47546385.1010708@dbservice.com \
--to=tom@dbservice.com \
--cc=arjan@infradead.org \
--cc=lenb@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox