Message-ID: <4322029C.2010904@funzi.de>
Date: Fri, 09 Sep 2005 23:46:04 +0200
From: Christopher Beppler <psiml@funzi.de>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050814)
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] hotplugging cpus via /sys/devices/system/cpu/
References: <4321F396.3010707@funzi.de> <20050909135556.A29542@unix-os.sc.intel.com>
In-Reply-To: <20050909135556.A29542@unix-os.sc.intel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1047
Lines: 32

Ashok Raj wrote:
> On Fri, Sep 09, 2005 at 01:41:58PM -0700, Christopher Beppler wrote:
> 
>>   [1.] One line summary of the problem:
>>   If I deactivate a CPU with /sys/devices/system/cpux and try to
>>   reactivate it, then the CPU doesn't start and the kernel prints out an
>>   oops.
>>
> 
> 
> Could you try this on 2.6.13-mm2? If this is due to a sending broadcast
> IPI related issue that should fix the problem.

No... the oops occurs furthermore...

> I should say i didnt try i386 in a while
> but i suspect some of the recent suspend/resume code required some
> modifications to the i386 hotplug code which might be getting in the way
> if you just try logical cpu hotplug alone without using it for suspend/resume.
> 
> Shaohua might know more about the status.
> 
> Cheers,
> ashok
> 
> 

-
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/