FYI. I recently added a thunderbolt hub and it's basically working ok
but I my log gets spammed with logs like this:
adding CRTC not allowed without modesets: requested 0x2, affected 0xf
Looking at the list it seems this is a known issue and there's work
afoot in this area but I get the impressio
On 30 July 2017 at 13:23, Greg Stark wrote:
> [drm:i915_hotplug_work_func [i915]] running encoder hotplug functions
> Jul 30 13:17:17 pixel kernel: [ 3221.929831]
> [drm:i915_hotplug_work_func [i915]] Connector HDMI-A-1 (pin 7)
> received hotplug event.
> Jul 30 13:17:
I updated my kernel to 4.11.0 and my laptop is now very slow and
laggy. I'm not sure if the graphics driver are directly causing the
slowdown or it's just systemd having trouble keeping up with the debug
messages though (systemd is consuming 4% of cpu just dealing with
messages which is impressivel
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
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
