From mboxrd@z Thu Jan  1 00:00:00 1970
From: Holger Schurig <hs4233@mail.mn-solutions.de>
Subject: Re: OOPS: getting an ACPI interrupt while in an ACPI interrupt hangs my box
Date: Wed, 10 Sep 2008 16:47:58 +0200
Message-ID: <200809101647.58567.hs4233@mail.mn-solutions.de>
References: <200809091605.07734.hs4233@mail.mn-solutions.de> <1221008490.3989.102.camel@yakui_zhao.sh.intel.com>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Return-path: <linux-acpi-owner@vger.kernel.org>
Received: from mx51.mymxserver.com ([85.199.173.110]:10213 "EHLO
	mx51.mymxserver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751761AbYIJOsJ (ORCPT
	<rfc822;linux-acpi@vger.kernel.org>); Wed, 10 Sep 2008 10:48:09 -0400
In-Reply-To: <1221008490.3989.102.camel@yakui_zhao.sh.intel.com>
Content-Disposition: inline
Sender: linux-acpi-owner@vger.kernel.org
List-Id: linux-acpi@vger.kernel.org
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org

> If the system is booted with the boot option of
> "processor.max_cstate=1", does the following warning message
> still exist?

Yes, if this did help, then only marginally.