Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: [OOPS] hotplugging cpus via /sys/devices/system/cpu/
Date: Fri, 16 Sep 2005 08:44:47 +0800
Message-ID: <59D45D057E9702469E5775CBB56411F16BBECA@pdsmsx406>
Thread-Topic: [OOPS] hotplugging cpus via /sys/devices/system/cpu/
Thread-Index: AcW1gPjHMu6fL1oGS5OnZ73hgLIlSQE1lbBA
From: "Li, Shaohua" <shaohua.li@intel.com>
To: "Raj, Ashok" <ashok.raj@intel.com>, "Christopher Beppler" <psiml@funzi.de>
Cc: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1236
Lines: 34


>
>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.
>
>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.
Sorry for the long delay, I missed this email (Ashok misspelled my email
address :)). The sysfs interface works for me. And please note I didn't
do status clear/__init call cleanup for non-intel CPU, as I haven't any
machine with non-intel CPUs here to test.

Thanks,
Shaohua
-
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/