All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Dave Airlie <airlied@redhat.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black
Date: Sat, 15 Aug 2015 15:32:39 +0200	[thread overview]
Message-ID: <55CF3F77.8030300@gmx.de> (raw)
In-Reply-To: <55C0B038.8090807@gmx.de>

On 08/04/2015 02:29 PM, Toralf Förster wrote:
> On 08/02/2015 09:43 AM, Pavel Machek wrote:
>> Any chance to bisect it?
> Did it.
> 
> FWIW: the mentioned commit was introduced between 3.18 and 3.19.
> But my system (hardened 64 bit Gentoo) did not suffer from it till version 4.0.8.
> The hardened kernel 4.1.x was the first where the bug was visible at my docked environment  too.
> 
> 
> 
> commit e7d6f7d708290da1b7c92f533444b042c79412e0
> Author: Dave Airlie <airlied@redhat.com>
> Date:   Mon Dec 8 13:23:37 2014 +1000
> 


FWIW the issue happens only if the system is docked.

Plugging in the VGA connector in parallel to the already plugged in DVI-D conenctor after wakeup from s2ram helps as a work around.
In this case then the external monitor shows again the KDE desktop.

After few seconds I can then plug off the VGA connector from the docking station and can continue with my work.


-- 
Toralf, pgp key: 872AE508 0076E94E
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Dave Airlie <airlied@redhat.com>
Subject: Re: 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black
Date: Sat, 15 Aug 2015 15:32:39 +0200	[thread overview]
Message-ID: <55CF3F77.8030300@gmx.de> (raw)
In-Reply-To: <55C0B038.8090807@gmx.de>

On 08/04/2015 02:29 PM, Toralf Förster wrote:
> On 08/02/2015 09:43 AM, Pavel Machek wrote:
>> Any chance to bisect it?
> Did it.
> 
> FWIW: the mentioned commit was introduced between 3.18 and 3.19.
> But my system (hardened 64 bit Gentoo) did not suffer from it till version 4.0.8.
> The hardened kernel 4.1.x was the first where the bug was visible at my docked environment  too.
> 
> 
> 
> commit e7d6f7d708290da1b7c92f533444b042c79412e0
> Author: Dave Airlie <airlied@redhat.com>
> Date:   Mon Dec 8 13:23:37 2014 +1000
> 


FWIW the issue happens only if the system is docked.

Plugging in the VGA connector in parallel to the already plugged in DVI-D conenctor after wakeup from s2ram helps as a work around.
In this case then the external monitor shows again the KDE desktop.

After few seconds I can then plug off the VGA connector from the docking station and can continue with my work.


-- 
Toralf, pgp key: 872AE508 0076E94E

  reply	other threads:[~2015-08-15 13:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 13:54 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black Toralf Förster
2015-07-29 13:54 ` Toralf Förster
2015-08-02  7:43 ` Pavel Machek
2015-08-02  7:43   ` Pavel Machek
2015-08-03  9:53   ` Toralf Förster
2015-08-03  9:53     ` Toralf Förster
2015-08-03 18:50     ` Toralf Förster
2015-08-03 18:50       ` Toralf Förster
2015-08-04 12:29   ` Toralf Förster
2015-08-04 12:29     ` Toralf Förster
2015-08-15 13:32     ` Toralf Förster [this message]
2015-08-15 13:32       ` Toralf Förster
2015-10-04 16:30     ` Toralf Förster
2015-10-04 16:30       ` Toralf Förster
2015-10-29 21:49       ` Pavel Machek
2015-10-30  9:38         ` Toralf Förster
2015-10-30  9:38           ` Toralf Förster
2015-12-03 16:06           ` 4.0 -> 4.1 regression " Pavel Machek
2015-12-03 16:06             ` Pavel Machek

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=55CF3F77.8030300@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=airlied@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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.