From: Daniel Vetter <daniel@ffwll.ch>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
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: Fri, 29 Nov 2013 08:56:17 +0100 [thread overview]
Message-ID: <20131129075616.GS27344@phenom.ffwll.local> (raw)
In-Reply-To: <alpine.LSU.2.11.1311282017400.4098@nerf07.vanv.qr>
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
next prev parent reply other threads:[~2013-11-29 7:55 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
2013-11-28 20:08 ` Jan Engelhardt
2013-11-29 7:56 ` Daniel Vetter [this message]
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=20131129075616.GS27344@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=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®