From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Linux 3.4 dom0 kernel error loading xen-acpi-processor: Input/output error Date: Sun, 12 May 2013 19:51:26 +0300 Message-ID: <20130512165126.GW11427@reaktio.net> References: <20130312205118.GN8912@reaktio.net> <20130315150527.GA16632@phenom.dumpdata.com> <20130315151934.GZ8912@reaktio.net> <20130315193706.GA8912@reaktio.net> <20130315211518.GA32252@phenom.dumpdata.com> <20130315213227.GB8912@reaktio.net> <20130317170047.GA13486@konrad-lan.dumpdata.com> <20130318130659.GA24560@phenom.dumpdata.com> <20130318170242.GF11427@reaktio.net> <20130318202051.GA30029@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20130318202051.GA30029@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: David Vrabel , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Mon, Mar 18, 2013 at 04:20:51PM -0400, Konrad Rzeszutek Wilk wrote: > > > > Hmm, on the R510 server where xen-acpi-processor doesn't work > > /sys/firmware/acpi/tables/dynamic/ is empty.. > > Pfff.. And 'cpuinfo' or 'cpufreq-info' when you boot baremetal gives > you different P-states? > > If so, is the DSDT different that when running under Xen? And > lasty, does it create any SSDT in the dynamic directory? > Finally I figured this one out.. in the end it was a BIOS settings/configuration issue. I found this: http://en.community.dell.com/techcenter/power-cooling/w/wiki/best-practices-in-power-management.aspx So I had to enable "OS Control" for "Power Management" in the Dell server BIOS, and after that the CPU P-states are available in the ACPI tables, and xen-acpi-processor driver loads and works OK in the dom0 kernel! (I'm almost 100% certain I tried that option already earlier, so I don't have any idea why it didn't work back then.. but *now* it seems to work!) For reference I'm using Intel L5640 Xeon CPU, and here's xenpm output for it: # xenpm get-cpufreq-states cpu id : 0 total P-states : 7 usable P-states : 7 current frequency : 1596 MHz P0 [2262 MHz]: transition [ 5] residency [ 59 ms] P1 [2261 MHz]: transition [ 0] residency [ 0 ms] P2 [2128 MHz]: transition [ 0] residency [ 0 ms] P3 [1995 MHz]: transition [ 0] residency [ 0 ms] P4 [1862 MHz]: transition [ 0] residency [ 0 ms] P5 [1729 MHz]: transition [ 0] residency [ 0 ms] *P6 [1596 MHz]: transition [ 5] residency [ 3437 ms] cpu id : 1 total P-states : 7 usable P-states : 7 current frequency : 1596 MHz P0 [2262 MHz]: transition [ 4] residency [ 103 ms] P1 [2261 MHz]: transition [ 0] residency [ 0 ms] P2 [2128 MHz]: transition [ 0] residency [ 0 ms] P3 [1995 MHz]: transition [ 0] residency [ 0 ms] P4 [1862 MHz]: transition [ 0] residency [ 0 ms] P5 [1729 MHz]: transition [ 0] residency [ 0 ms] *P6 [1596 MHz]: transition [ 4] residency [ 5893 ms] .. and so on. Thanks a lot Konrad for your help on this! -- Pasi