On Wed, Jan 14, 2015 at 12:50:46PM +0200, Ander Conselvan de Oliveira wrote: > On 01/14/2015 12:47 PM, Jani Nikula wrote: > >On Tue, 13 Jan 2015, Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@xxxxxxxxx> wrote: > >>If QUIRK_PIPEA_FORCE is necessary, intel_sanitize_crtc() might trigger > >>a mode set. In that case, if pipe A is disabled and pipe B is mapped to > >>plane B, that mode set happens before the mapping is fixed. Due to the > >>wrong state, the call to disable pipe B disables plane A (which is > >>already disabled) and later an assertion for plane B being enabled > >>(while it should have been disabled) is triggered. > >> > >>References: https://bugs.freedesktop.org/show_bug.cgi?id=72782 > > > >If the patch is expected to fix the bug, please use Bugzilla:. If you're > >referencing a bug because it's otherwise relevant, please use > >References:. > > > >Which one is this? > > This showed up in the dmesg attached to the referenced bug, but is > not the root cause of the reported problem. As far as I know, there > is no open bug for this particular issue. But that machine should not be using QUIRK_PIPEA_FORCE... What I expect is happening is that the BIOS sets up the LVDS on the "wrong" pipe. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
