All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
	Dmitry Adamushko <dmitry.adamushko@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Avi Kivity <avi@qumranet.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [BUG] CFS vs cpu hotplug
Date: Tue, 01 Jul 2008 18:09:02 +0800	[thread overview]
Message-ID: <486A023E.8060203@cn.fujitsu.com> (raw)
In-Reply-To: <20080701093124.GC31309@elte.hu>

Ingo Molnar wrote:
> * Lai Jiangshan <laijs@cn.fujitsu.com> wrote:
> 
>> The following oops still occurred whether this patch is applied or not.
> 
>>  [<ffffffff8059372c>] notifier_call_chain+0x33/0x5b
>>  [<ffffffff802476a9>] __raw_notifier_call_chain+0x9/0xb
>>  [<ffffffff802476ba>] raw_notifier_call_chain+0xf/0x11
>>  [<ffffffff805736d6>] _cpu_down+0x191/0x256
>>  [<ffffffff805737c1>] cpu_down+0x26/0x36
>>  [<ffffffff805749c1>] store_online+0x32/0x75
>>  [<ffffffff803d1982>] sysdev_store+0x24/0x26
>>  [<ffffffff802d2551>] sysfs_write_file+0xe0/0x11c
>>  [<ffffffff80290e6b>] vfs_write+0xae/0x137
>>  [<ffffffff802913d3>] sys_write+0x47/0x70
>>  [<ffffffff8020b1eb>] system_call_after_swapgs+0x7b/0x80
> 
> hm, there were multiple problems in this area and a lot of dormant bugs. 
> Do you have this recent upstream commit in your tree:
No, I'll apply this patch and test it again. Thanks!
> 
> | commit fcb43042ef55d2f46b0efa5d7746967cef38f056
> | Author: Zhang, Yanmin <yanmin_zhang@linux.intel.com>
> | Date:   Tue Jun 24 16:06:23 2008 +0800
> |
> |    x86: fix cpu hotplug crash
> |
> |    Vegard Nossum reported crashes during cpu hotplug tests:
> |
> |      http://marc.info/?l=linux-kernel&m=121413950227884&w=4
> 
> ?
> 
> 	Ingo
> 
> 
> 




  reply	other threads:[~2008-07-01 10:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 16:19 [BUG] CFS vs cpu hotplug Heiko Carstens
2008-06-19 18:05 ` Peter Zijlstra
2008-06-19 18:14   ` Peter Zijlstra
2008-06-19 21:14     ` Heiko Carstens
2008-06-19 21:26       ` Peter Zijlstra
2008-06-19 21:17   ` Heiko Carstens
2008-06-19 21:32   ` Peter Zijlstra
2008-06-19 21:49     ` Heiko Carstens
2008-06-20  8:51       ` Peter Zijlstra
2008-06-20 22:19         ` Heiko Carstens
2008-06-20 11:44   ` Dmitry Adamushko
2008-06-20 22:23     ` Heiko Carstens
2008-06-25 22:12 ` Dmitry Adamushko
2008-06-28 22:16   ` Dmitry Adamushko
2008-06-29  6:55     ` Ingo Molnar
2008-06-30  9:07     ` Heiko Carstens
2008-06-30  9:17       ` Ingo Molnar
2008-07-01  9:22         ` Lai Jiangshan
2008-07-01  9:31           ` Ingo Molnar
2008-07-01 10:09             ` Lai Jiangshan [this message]
2008-07-02  7:13             ` Lai Jiangshan
2008-07-02  8:50               ` Dmitry Adamushko
2008-07-02  9:23                 ` Lai Jiangshan
2008-07-07 10:26                   ` Miao Xie
2008-07-07 11:31                     ` Dmitry Adamushko
  -- strict thread matches above, loose matches on Subject: below --
2008-07-09 22:32 Dmitry Adamushko
2008-07-10  7:30 ` Heiko Carstens
2008-07-10  7:39   ` Ingo Molnar

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=486A023E.8060203@cn.fujitsu.com \
    --to=laijs@cn.fujitsu.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=avi@qumranet.com \
    --cc=dmitry.adamushko@gmail.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.