From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Len Brown <lenb@kernel.org>
Cc: Vincent Gerris <vgerris@gmail.com>,
Hans de Goede <hdegoede@redhat.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Jochen Hein <jochen@jochen.org>,
Linux PM <linux-pm@vger.kernel.org>,
jacob.jun.pan@linux.intel.com, Vinod Koul <vinod.koul@intel.com>,
"Prusty, Subhransu S" <subhransu.s.prusty@intel.com>
Subject: Re: [PATCH] intel_idle: work around errate VLP52 on Baytrail CPUs
Date: Wed, 11 Jan 2017 15:22:44 -0800 [thread overview]
Message-ID: <20170111152244.360e8a82@jacob-builder> (raw)
In-Reply-To: <CAJvTdKnuiaa4WcDYORe1O8R48dbawX1V9McbpMh-9AyAc5DLZg@mail.gmail.com>
On Wed, 11 Jan 2017 18:14:12 -0500
Len Brown <lenb@kernel.org> wrote:
> Re: powertop
>
> turbostat is more useful. The pre-release I uploaded to the bug
> report includes some baytrail specific support:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=109051#c661
>
> > I saw your patch for auto-demotion, I will test it and report
> > within a few days. I will also do further testing with the 4.9
> > kernel. I hope we can get things stable one way or the other :).
>
> Current thinking is that we have multiple issues here, and enabling
> auto-demotion
> simply hides the actual root causes.
>
> Sound is one known root cause, as Jacob pointed out.
> Hopefully we'll have a fix for that one shortly.
>
+Vinod & Subhransu
Could you send out Baytrail VLP70 SST driver workaround patch for
testing?
> I'm testing w/o sound, and still can provoke a failure in under 30
> minutes.
>
> Len Brown, Intel Open Source Technology Center
[
prev parent reply other threads:[~2017-01-11 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 18:19 [PATCH] intel_idle: work around errate VLP52 on Baytrail CPUs Jochen Hein
2016-12-19 19:43 ` Rafael J. Wysocki
[not found] ` <CA+8K-g=fXN9TWWxkV1AEEjXJLhwJEQ2PB434gKQ9Z7bL=yf+zA@mail.gmail.com>
2016-12-27 17:24 ` Vincent Gerris
2016-12-27 20:37 ` Len Brown
2016-12-27 20:44 ` Jochen Hein
2016-12-27 21:27 ` Len Brown
2016-12-28 12:56 ` Vincent Gerris
2016-12-28 18:47 ` Jacob Pan
2017-01-11 23:14 ` Len Brown
2017-01-11 23:22 ` Jacob Pan [this message]
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=20170111152244.360e8a82@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=jochen@jochen.org \
--cc=lenb@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=subhransu.s.prusty@intel.com \
--cc=vgerris@gmail.com \
--cc=vinod.koul@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.