From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: "Vegard Nossum" <vegard.nossum@gmail.com>
Cc: Yanmin <yanmin_zhang@linux.intel.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Ingo Molnar" <mingo@elte.hu>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Dhaval Giani" <dhaval@linux.vnet.ibm.com>,
"Gautham R Shenoy" <ego@in.ibm.com>,
"Heiko Carstens" <heiko.carstens@de.ibm.com>,
miaox@cn.fujitsu.com, "Lai Jiangshan" <laijs@cn.fujitsu.com>,
"Avi Kivity" <avi@qumranet.com>,
linux-kernel@vger.kernel.org
Subject: Re: v2.6.26-rc9: kernel BUG at kernel/sched.c:5858!
Date: Thu, 10 Jul 2008 16:03:25 +0200 [thread overview]
Message-ID: <b647ffbd0807100703q442a9825hb857c321452027e7@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0807100604p70c2fec6geca65b2ba772dea@mail.gmail.com>
2008/7/10 Vegard Nossum <vegard.nossum@gmail.com>:
> On Thu, Jul 10, 2008 at 2:50 PM, Dmitry Adamushko
> <dmitry.adamushko@gmail.com> wrote:
>> 2008/7/10 Vegard Nossum <vegard.nossum@gmail.com>:
>>> On Thu, Jul 10, 2008 at 1:59 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> Looks like CPU hotplug still has some problems. Just got this on
>>>> latest mainline, and I couldn't find the exact same report on LKML
>>>> or kerneloops, maybe it can be helpful for debugging the existing
>>>> problem(s)?
>>>>
>
> [...]
>
>> Does a patch from Miao Xie available via the link below makes this
>> problem disappear? Both bugs are likely to have the same cause.
>>
>> http://lkml.org/lkml/2008/7/7/75
>
> Yep, it does, nice, thanks!
>
> Will these two patches (yours and Miao Xie's) be queued for 2.6.26 already?
Miao Xie's patch addresses a problem by fixing its consequence. In
general, an 'offline' cpu must not be visible for any kind of
load-balancing at this point. So I'd rather like to understand and
address the root cause of this mis-behavior.
Regarding new crashes. Do you get them
(1) after a few cpu offline / onlines ?
(2) on a freshly booted system?
(3) (1) or (2) but only with Miao Xie's patch (should not be (2) then)
(4) something else?
TIA,
--
Best regards,
Dmitry Adamushko
next prev parent reply other threads:[~2008-07-10 14:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 11:59 v2.6.26-rc9: kernel BUG at kernel/sched.c:5858! Vegard Nossum
2008-07-10 12:12 ` Vegard Nossum
2008-07-10 12:50 ` Dmitry Adamushko
2008-07-10 13:04 ` Vegard Nossum
2008-07-10 13:17 ` Vegard Nossum
2008-07-10 13:33 ` Vegard Nossum
2008-07-10 13:43 ` Vegard Nossum
2008-07-10 14:03 ` Dmitry Adamushko [this message]
2008-07-10 14:16 ` Vegard Nossum
2008-07-10 15:06 ` Vegard Nossum
2008-07-10 19:49 ` Vegard Nossum
2008-07-10 20:16 ` Dmitry Adamushko
2008-07-11 5:49 ` Vegard Nossum
2008-07-11 9:02 ` Dmitry Adamushko
2008-07-11 11:04 ` Vegard Nossum
2008-07-11 11:46 ` Dmitry Adamushko
2008-07-11 17:51 ` Vegard Nossum
2008-07-11 18:00 ` Vegard Nossum
2008-07-11 23:42 ` Dmitry Adamushko
2008-07-10 20:20 ` Rafael J. Wysocki
2008-07-11 5:23 ` Vegard Nossum
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=b647ffbd0807100703q442a9825hb857c321452027e7@mail.gmail.com \
--to=dmitry.adamushko@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=avi@qumranet.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=ego@in.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=vegard.nossum@gmail.com \
--cc=yanmin_zhang@linux.intel.com \
/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.