Return-Path: <linux-kernel-owner+w=401wt.eu-S1759429AbXE1Exq@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1759429AbXE1Exq (ORCPT <rfc822;w@1wt.eu>);
	Mon, 28 May 2007 00:53:46 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753307AbXE1Exj
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 28 May 2007 00:53:39 -0400
Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:58327 "EHLO
	fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752274AbXE1Exj (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 28 May 2007 00:53:39 -0400
Date: Mon, 28 May 2007 13:53:30 +0900
Message-ID: <87k5utblbp.wl%takeuchi_satoru@jp.fujitsu.com>
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
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/21.4 (i486-pc-linux-gnu)
 MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1795
Lines: 80

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/