All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Dave Airlie <airlied@redhat.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Fwd: 3.18.3->4 : external monitor is black after wakeup of a docked system after s2ram
Date: Tue, 03 Feb 2015 16:46:07 +0100	[thread overview]
Message-ID: <54D0ED3F.6070404@gmx.de> (raw)
In-Reply-To: <54CFC0D0.8030201@gmx.de>

This commits breaks a working configuration here - reverting it let both version 3.18.4 and 3.18.5 working fine again at a hardened Gentoo Linux


commit ddf6f9a4c9fb1c72ea2e8d196c9a580a8e914dbd
Author: Dave Airlie <airlied@redhat.com>
Date:   Mon Dec 8 13:23:37 2014 +1000

    drm/i915: resume MST after reading back hw state
    
    commit e7d6f7d708290da1b7c92f533444b042c79412e0 upstream.
    
    Otherwise the MST resume paths can hit DPMS paths
    which hit state checker paths, which hit WARN_ON,
    because the state checker is inconsistent with the
    hw.
    
    This fixes a bunch of WARN_ON's on resume after
    undocking.
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Signed-off-by: Jani Nikula <jani.nikula@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>


On 02/02/2015 07:24 PM, Toralf Förster wrote:
> In the mean while I have to correct it - it is reliable.
> So something between 3.18.3 and 3.18.4 break a docking system configuration in that manenr, that after resume the external (iand internal X11 screen) is black.
> 
> 
> -------- Forwarded Message --------
> Subject: 3.18.3->4 : external monitor is black after wakeup of a docked system after s2ram
> Date: Sat, 31 Jan 2015 16:47:45 +0100
> From: Toralf Förster <toralf.foerster@gmx.de>
> To: Linux Kernel <linux-kernel@vger.kernel.org>
> 
> Happened 2 times here (but not always) that a docked Lenovo T440s (intel graphic) doesn't show anything at the external display (KDE 4.13.3). System is a hardened stable 64 bit Gentoo Linux
> 
> Nothing suspicious in the log however.
> 
> Known issue ?
> 


-- 
Toralf
pgp key: 7B1A 07F4 EC82 0F90 D4C2  8936 872A E508 0076 E94E

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2015-02-03 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31 15:47 3.18.3->4 : external monitor is black after wakeup of a docked system after s2ram Toralf Förster
2015-02-02 18:24 ` Fwd: " Toralf Förster
2015-02-03 15:46   ` Toralf Förster [this message]

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=54D0ED3F.6070404@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.