linux-kernel - Re: i915: pipe state still does not match

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20131130212810.GA12866@nuc-i3427.alporthouse.com>
Date:	Sat, 30 Nov 2013 21:28:10 +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 Sat, Nov 30, 2013 at 05:31:34PM +0100, Jan Engelhardt wrote:
> 
> 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@...is-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?

I'd say it was just the KMS transition from the X mode to the fbcon mode
that triggers the inconsistent state warning. The warning is just that
the hardware state after the mode change does not match our expectations
- often this is a result of a buggy state readback, but sometimes it
does indicate a more severe bug in our mode programming.
-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/