From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Borislav Petkov <bp@alien8.de>,
Kristen Carlson Accardi <kristen@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: 37afb0003242 ("cpufreq: intel_pstate: Use ACPI perf configuration") makes intel_pstate kaputt
Date: Tue, 17 Nov 2015 09:06:30 -0800 [thread overview]
Message-ID: <1447779990.2778.47.camel@spandruv-desk3.jf.intel.com> (raw)
In-Reply-To: <7244050.99ueqT3SFL@vostro.rjw.lan>
On Tue, 2015-11-17 at 15:38 +0100, Rafael J. Wysocki wrote:
> On Tuesday, November 17, 2015 10:09:47 AM Borislav Petkov wrote:
> > Hi,
> >
[...]
> > during boot.
Also can you try with processor.ignore_ppc=1 in kernel command line.
Thanks,
Srinivas
> >
> > When I boot with "intel_pstate=no_acpi" it boosts normally to 3.4GHz and
> > above and turbostat says:
> >
> > CPU Avg_MHz %Busy Bzy_MHz TSC_MHz
> > - 3392 99.92 3400 2895
> > 0 3395 99.96 3400 2897
> > 1 3390 99.88 3400 2895
> > 2 3391 99.89 3400 2895
> > 3 3391 99.95 3400 2893
> >
> > which is what it should be saying. :)
>
> Well, sorry for the breakage.
>
> acpidump output would help to diagnose this I suppose.
>
> Thanks,
> Rafael
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-11-17 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151117090947.GC8819@pd.tnic>
2015-11-17 14:38 ` 37afb0003242 ("cpufreq: intel_pstate: Use ACPI perf configuration") makes intel_pstate kaputt Rafael J. Wysocki
2015-11-17 14:14 ` Borislav Petkov
2015-11-17 17:06 ` Srinivas Pandruvada [this message]
2015-11-17 18:14 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1447779990.2778.47.camel@spandruv-desk3.jf.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=bp@alien8.de \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox