[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131127110836.GA6087@nuc-i3427.alporthouse.com>
Date: Wed, 27 Nov 2013 11:08:36 +0000
From: Chris Wilson <chris@...is-wilson.co.uk>
To: Jan Engelhardt <jengelh@...i.de>
Cc: daniel.vetter@...ll.ch, dri-devel@...ts.freedesktop.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: i915: pipe state still does not match
On Wed, Nov 27, 2013 at 11:59:56AM +0100, Jan Engelhardt wrote:
> Greetings.
>
>
> 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.
>
> I have a fb setup to span two crtcs in below's configuration,
> and the kernel problem is easily triggerable for me by moving
> an Xv window (such as by using mplayer) forth and back
> between the two crtc.
> The problem did not exist in 3.9.9.
>
> > xrandr
> Screen 0: minimum 320 x 200, current 1280 x 1624, maximum 32767 x 32767
> LVDS1 connected primary 1024x600+0+1024 (normal left inverted right x axis y axis) 220mm x 129mm
> 1024x600 60.0*+
> 800x600 60.3 56.2
> 640x480 59.9
> VGA1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm
> 1280x1024 60.0*+ 75.0 72.0
> 1152x864 75.0
> 1024x768 75.1 70.1 60.0
> 832x624 74.6
> 800x600 72.2 75.0 60.3
> 640x480 75.0 72.8 66.7 60.0
> 720x400 70.1
> 640x350 70.1
> VIRTUAL1 disconnected (normal left inverted right x axis y axis)
X terminating is entirely unconnected with that *ERROR*. Can you please
attach your Xorg.0.log with the crash information?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists