On Sat, Nov 28, 2015 at 3:53 PM, Ville Syrjälä
wrote:
> Use drm.debug=0xe unless you really want to debug the atomic code (which
> is where all this spew comes from).
Thanks.
I'm trying to get debug info to report the freezes that still happen
on my Chromebook Pixel even after the fix that appar
On Tue, Nov 17, 2015 at 05:11:05PM +0200, Jani Nikula wrote:
> On Tue, 17 Nov 2015, Marc MERLIN wrote:
> > So, this is probably the 3rd time I send such a report with different
> > kernels and get 0 response.
> > Is this a write only list and no one is really seeing any of them, or is
> > this an
On Sat, Nov 28, 2015 at 02:57:17PM +, Greg Stark wrote:
> I set set the debugging flag as suggested by the online docs for
> reporting GPU hang bugs and I'm seeing the logs fill up with messages.
> I didn't think that was surprising but actually poking around it looks
> like they don't get lots
I set set the debugging flag as suggested by the online docs for
reporting GPU hang bugs and I'm seeing the logs fill up with messages.
I didn't think that was surprising but actually poking around it looks
like they don't get lots of messages generally, all the messages are
generated by the mouse
Similar to
commit 37ca8d4ccd9860df0747aa2ea281a3c9c4bf8826
Author: Ville Syrjälä
Date: Fri Oct 30 19:20:27 2015 +0200
drm/i915: Enable PCH FIFO underruns later on ILK/SNB/IVB
we can only enable fifo underrun reporting when using the fdi/lpt
after everything is set up and after a bit of wa
The runtime PM core doesn't treat EBUSY and EAGAIN retvals from the driver
suspend hooks as errors, but they still show up as errors in dmesg. Tune
them down.
One problem caused by this was noticed by Daniel: the i915 driver
returns EAGAIN to signal a temporary failure to suspend and as a request
