On Thu, Nov 28, 2013 at 09:08:45PM +0100, Jan Engelhardt wrote: > On Wednesday 2013-11-27 12:08, Chris Wilson wrote: > >On Wed, Nov 27, 2013 at 11:59:56AM +0100, Jan Engelhardt wrote: > >> > >> Despite the i915/drm fixes added in v3.11.8, the X server still > >> terminates due to some pipe state bug in 3.11.9. > > > >X terminating is entirely unconnected with that *ERROR*. > > Are you sure? Whenever X crashed, that inteldrv kernel message > was showing up in dmesg. > Affected versions: > xorg-x11-server-1.14.3.901 > xf86-video-intel-2.99.906-4.1.x86_64 > Working versions: > xorg-x11-server-1.13.2 > xf86-video-intel-2.20.19
For the ERROR the kernel is the important part. I can be that it's triggered by userspace doing something funny (and likely, sinc there's a good chance you're hitting a less well tested path when crashing). But it's a kernel issue. To track the kernel issue down can you please boot with drm.debug=0xe added to your bootline, reproduce the issue and then attach the complete dmesg? Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
