On Fri, Jun 14, 2013 at 12:32 PM, Daniel Vetter wrote:
> On Fri, Jun 14, 2013 at 9:13 PM, Stéphane Marchesin
> wrote:
>> On Wed, Jun 12, 2013 at 2:41 AM, Chris Wilson
>> wrote:
>>> On Tue, Jun 11, 2013 at 03:49:26PM -0700, Stéphane Marchesin wrote:
It's basically the same deal as the RC6+
On Fri, Jun 14, 2013 at 9:13 PM, Stéphane Marchesin
wrote:
> On Wed, Jun 12, 2013 at 2:41 AM, Chris Wilson
> wrote:
>> On Tue, Jun 11, 2013 at 03:49:26PM -0700, Stéphane Marchesin wrote:
>>> It's basically the same deal as the RC6+ issues on ivy bridge
>>> except this time with RC6 on sandy brid
On Wed, Jun 12, 2013 at 2:41 AM, Chris Wilson wrote:
> On Tue, Jun 11, 2013 at 03:49:26PM -0700, Stéphane Marchesin wrote:
>> It's basically the same deal as the RC6+ issues on ivy bridge
>> except this time with RC6 on sandy bridge. Like last time the
>> core of the issue is that the timings don'
On Tue, Jun 11, 2013 at 03:49:26PM -0700, Stéphane Marchesin wrote:
> It's basically the same deal as the RC6+ issues on ivy bridge
> except this time with RC6 on sandy bridge. Like last time the
> core of the issue is that the timings don't work 100% with our
> voltage regulator. So from time to t
It's basically the same deal as the RC6+ issues on ivy bridge
except this time with RC6 on sandy bridge. Like last time the
core of the issue is that the timings don't work 100% with our
voltage regulator. So from time to time, the kernel will print
a warning message about the GPU not getting out o
