mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>,
	Zwane Mwaikambo <zwane@arm.linux.org.uk>,
	Nathan Lynch <nathanl@austin.ibm.com>,
	Joel Schopp <jschopp@austin.ibm.com>,
	Ashok Raj <ashok.raj@intel.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Gautham R Shenoy <ego@in.ibm.com>,
	Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Subject: [BUG] CPU hotplug: system hang on CPU hot remove during oprofile
Date: Mon, 28 May 2007 13:53:30 +0900	[thread overview]
Message-ID: <87k5utblbp.wl%takeuchi_satoru@jp.fujitsu.com> (raw)

Hi,

I found a bug on CPU hotplug. If oprofile is running, CPU hot remove causes
system hang. I only confirm that this problem occurs on my ia64 box. I'm glad
if someone report about other arch.

How to reproduce
================

1) start oprofile

  # opcontrol --start

2) offline a CPU.

  # echo 0 >/sys/devices/system/cpu/cpu1/online 

Expected Result
===============

Succeed to remove CPU

Actual Result
=============

See the following console log.

  # opcontrol --start
  Detected stale lock file. Removing.
  Using 2.6+ OProfile kernel interface.
  Reading module info.
  Running perfmon child on CPU0.
  Waiting on CPU0
  Perfmon child up on CPU0
  Running perfmon child on CPU1.
  Waiting on CPU1
  Perfmon child up on CPU1
  Running perfmon child on CPU2.
  Waiting on CPU2
  Perfmon child up on CPU2
  Running perfmon child on CPU3.
  Waiting on CPU3
  Perfmon child up on CPU3
  Running perfmon child on CPU4.
  Waiting on CPU4
  Perfmon child up on CPU4
  Running perfmon child on CPU5.
  Waiting on CPU5
  Perfmon child up on CPU5
  Running perfmon child on CPU6.
  Waiting on CPU6
  Perfmon child up on CPU6
  Running perfmon child on CPU7.
  Waiting on CPU7
  Perfmon child up on CPU7
  Using log file /var/lib/oprofile/oprofiled.log
  Daemon started.
  PFM_START on CPU1
  PFM_START on CPU4
  PFM_START on CPU0
  Profiler running.
  PFM_START on CPU3
  PFM_START on CPU5
  PFM_START on CPU2
  PFM_START on CPU7
  PFM_START on CPU6
  
  # echo 0 >/sys/devices/system/cpu/cpu1/online 
  
  <SYSTEM HANG UP here!>


Thanks,

Satoru

             reply	other threads:[~2007-05-28  4:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28  4:53 Satoru Takeuchi [this message]
2007-05-28  9:12 ` Russell King

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=87k5utblbp.wl%takeuchi_satoru@jp.fujitsu.com \
    --to=takeuchi_satoru@jp.fujitsu.com \
    --cc=ashok.raj@intel.com \
    --cc=ego@in.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jschopp@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathanl@austin.ibm.com \
    --cc=rusty@rustcorp.com.au \
    --cc=vatsa@in.ibm.com \
    --cc=zwane@arm.linux.org.uk \
    /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

Powered by JetHome