[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1A7043D5F58CCB44A599DFD55ED4C948452FDAA3@FMSMSX106.amr.corp.intel.com>
Date: Wed, 2 Apr 2014 21:50:03 +0000
From: "Brown, Len" <len.brown@...el.com>
To: "Gortmaker, Paul (Wind River)" <paul.gortmaker@...driver.com>
CC: "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
Arne Bockholdt <linux-kernel@...kholdt.com>,
Jiang Liu <jiang.liu@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Regression in intel_idle on Avaton/Rangely Mohon Peak board
> > I'd be interested in the acpi_idle output above for both the
> > new and old boards to see if they are exporting different states
> > on the two boards.
>
> Could be ; I can probably get access to the newer one again too, if
> that will be useful.
yes, please.
> >
> > dmidecode isn't useful in this case. The CPUID in /proc/cpuinfo
> > may be useful if the problem turns out to be associated with
> > some stepping.
>
> The dmidecode info I'd posted indicated that the steppings were
> unnchanged. I can get the /proc/cpuinfo tomorrow, but I figured
> the dmidecode stepping info was accurate. Is it not reliable?
DMI is useful to get the BIOS version string, not much else.
Here you want the output from the CPUID instruction,
which is displayed as family/model/stepping in /proc/cpuinfo
thanks,
-Len
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists