From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Linux 3.4 dom0 kernel error loading xen-acpi-processor: Input/output error Date: Fri, 15 Mar 2013 11:05:27 -0400 Message-ID: <20130315150527.GA16632@phenom.dumpdata.com> References: <20130303185347.GH8912@reaktio.net> <20130305174515.GA24062@phenom.dumpdata.com> <20130306204139.GS8912@reaktio.net> <20130306210127.GT8912@reaktio.net> <20130306212147.GU8912@reaktio.net> <20130307002934.GB12421@phenom.dumpdata.com> <20130307074808.GV8912@reaktio.net> <20130308202457.GA21875@phenom.dumpdata.com> <20130308221820.GE8912@reaktio.net> <20130312205118.GN8912@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20130312205118.GN8912@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Cc: David Vrabel , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Tue, Mar 12, 2013 at 10:51:18PM +0200, Pasi K=E4rkk=E4inen wrote: > On Sat, Mar 09, 2013 at 12:18:20AM +0200, Pasi K=E4rkk=E4inen wrote: > > > > = > > > > I don't seem to have _PCT on my Ivy Bridge i7 laptop.. = > > > > = > > > > > In your case then .. lets go back to the start - the driver faile= d with -EIO > > > > > and it was v3.4.x kernel? Now that I've figured out the regressio= n with v3.9 > > > > > I can take a look at this. > > > > > = > > > > = > > > > Ok. > > > > = > > > > So the problem for me with Linux 3.4.32 kernel is "modprobe xen-acp= i-processor" fails: > > > > initcall xen_acpi_processor_init+0x0/0x6b0 [xen_acpi_processor] ret= urned with error code -5 > > > > = > > > = > > > Great :-( On my box (SandyBridge i3 2100, MS-7680) it installs just f= ine. This is > > > v3.4.22 with = > > > = > > > cat linux-build/.config|grep PROCESSOR > > > CONFIG_ACPI_PROCESSOR=3Dy > > > CONFIG_ACPI_PROCESSOR_AGGREGATOR=3Dm > > > CONFIG_XEN_ACPI_PROCESSOR=3Dm > > > = > > = > > I'm using: > > = > > CONFIG_ACPI_PROCESSOR=3Dy > > CONFIG_ACPI_PROCESSOR_AGGREGATOR=3Dm > > CONFIG_XEN_ACPI_PROCESSOR=3Dm > > = > = > Do you see _PCT on your SandyBridge i3 DSDT? = No. I am actually not seeing a lot of them, but I am still seeing P-states?! 15:03:49 # 21 :/sys/firmware/acpi/tables/ = > xenpm get-cpufreq-para 0 cpu id : 0 affected_cpus : 0 cpuinfo frequency : max [3100000] min [1600000] cur [1600000] scaling_driver : acpi-cpufreq scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 3100000 3000000 2900000 2800000 2700000 2600000 2500= 000 2400000 2300000 2200000 2100000 2000000 1900000 1800000 1700000 *1600000 scaling frequency : max [3100000] min [1600000] cur [1600000] WTF!? And also the C-states: > xenpm get-cpuidle-states 0 Max possible C-state: C7 cpu id : 0 total C-states : 3 idle time(ms) : 543153 C0 : transition [ 45047] residency [ 11006 ms] C1 : transition [ 14099] residency [ 13076 ms] C2 : transition [ 30948] residency [ 527658 ms] pc2 : [ 13698 ms] pc3 : [ 0 ms] pc6 : [ 484534 ms] pc7 : [ 0 ms] cc3 : [ 0 ms] cc6 : [ 525300 ms] cc7 : [ 0 ms] I need to look back at my notes on how the _PCT, _PSS, _Pwhatevername work.