From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jan Engelhardt <jengelh@inai.de>
Cc: daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: i915: pipe state still does not match
Date: Wed, 27 Nov 2013 11:08:36 +0000 [thread overview]
Message-ID: <20131127110836.GA6087@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1311271156060.20996@nerf07.vanv.qr>
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
next prev parent reply other threads:[~2013-11-27 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 10:59 Jan Engelhardt
2013-11-27 11:08 ` Chris Wilson [this message]
2013-11-28 20:08 ` Jan Engelhardt
2013-11-29 7:56 ` Daniel Vetter
2013-11-29 10:48 ` Chris Wilson
2013-11-30 16:31 ` Jan Engelhardt
2013-11-30 21:28 ` Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131127110836.GA6087@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jengelh@inai.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®