From: Jan Engelhardt <jengelh@inai.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
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: Sat, 30 Nov 2013 17:31:34 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.11.1311301727440.31825@nerf07.vanv.qr> (raw)
In-Reply-To: <20131129104825.GE27806@nuc-i3427.alporthouse.com>
On Friday 2013-11-29 11:48, Chris Wilson wrote:
>> What I could collect so far:
>
>Thanks, I broke the handling of cropped XvImages along the fast paths.
>It should be fixed by:
>
>commit fd007d9d465b9b3ddbbaf769931ec921a6f5ecb8
>Author: Chris Wilson <chris@chris-wilson.co.uk>
>Date: Thu Nov 28 21:13:33 2013 +0000
>
> sna/video: Correct handling of cropped images along packed fast path
I didn't manage to crash X within an hour, so that's commit is looking
good.
The kernel error message for i915 pipe state however still appears -
namely, whenever the X server is terminating, including "reasonably
proper" terminations induced with sending SIGTERM to the X process.
Could it be that the i915 module does not handle sudden shutdowns
(which however can occur at any time) of the /dev/dri/cardN file
descriptor well enough?
next prev parent reply other threads:[~2013-11-30 16:31 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
2013-11-29 10:48 ` Chris Wilson
2013-11-30 16:31 ` Jan Engelhardt [this message]
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=alpine.LSU.2.11.1311301727440.31825@nerf07.vanv.qr \
--to=jengelh@inai.de \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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®