dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Dieter Nützel" <Dieter@nuetzel-hh.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	Rex Zhu <Rex.Zhu@amd.com>,
	dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Re: [pull] amdgpu dc drm-next-4.15-dc
Date: Thu, 26 Oct 2017 16:10:54 +0200	[thread overview]
Message-ID: <cab8fe1180a059f1856c876bd3fe8551@nuetzel-hh.de> (raw)
In-Reply-To: <88d6b3afed0d97d3416e51448938a97f@nuetzel-hh.de>

Hello Alex & Rex,

any progress?
The 'screen blank' (monitor standby mode) is really annoying.

Thanks,
Dieter

Am 23.10.2017 03:03, schrieb Dieter Nützel:
> Am 22.10.2017 23:48, schrieb Dieter Nützel:
>> Am 21.10.2017 23:22, schrieb Alex Deucher:
>>> Hi Dave,
>>> 
>>> Last batch of new stuff for DC. Highlights:
>>> - Fix some memory leaks
>>> - S3 fixes
>>> - Hotplug fixes
>>> - Fix some CX multi-display issues
>>> - MST fixes
>>> - DML updates from the hw team
>>> - Various code cleanups
>>> - Misc bug fixes
>> 
>> Now this tree has the same fan regression as 'amd-staging-drm-next'
>> startet with 0944c350c8eddf4064e7abb881dd245032fdfa23.
>> 
>> Look here:
>> [amd-staging-drm-next] regression - no fan info (sensors) on RX580
>> https://lists.freedesktop.org/archives/amd-gfx/2017-October/014065.html
>> 
>> Second:
>> KDE's greeter 'kdm_greet' (login screen went into dpms) and KDE's
>> 'screen blank' (energy saving / dpms off) never came back. All I can
>> do is a clean reboot. So I have to disable all 'dpms'.
>> But I could attach gdb remotely on it.
>> 'kdm_greet' hang in 'poll'.
>> Nothing alarming in 'dmesg' and 'Xorg.0.log'. (Both available taken
>> from 'amd-staging-drm-next' if needed).
> 
> Hello Alex and Rex,
> 
> I've found good hint from Jan (randomsalad) on phoronix for the
> 'screen blank' (monitor standby mode):
> https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/984483-amdgpu-dc-gets-a-final-batch-of-changes-before-linux-4-15?p=984555#post984555
> 
> My Reply:
> https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/984483-amdgpu-dc-gets-a-final-batch-of-changes-before-linux-4-15?p=984581#post984581
> 
> I can swear, that I could 'return' one time (the first time, maybe due
> to only warm reboot) on 'drm-next-4.15-dc-wip' directly from within
> KDE session with replugging the video cable, but for all later tests
> on both kernels I have to blindly switching back to login screen
> (kdm_greet) and then replugging the video cable.
> 
> For me these regression started with 'amd-staging-drm-next' much
> earlier than with the latest commit.
> 
> Dieter
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-10-26 14:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-21 21:22 [pull] amdgpu dc drm-next-4.15-dc Alex Deucher
     [not found] ` <1508620979-2628-1-git-send-email-alexander.deucher-5C7GfCeVMHo@public.gmane.org>
2017-10-22 21:48   ` Dieter Nützel
     [not found]     ` <da505e834d1a47cf9a7abcce33545fd9-0hun7QTegEsDD4udEopG9Q@public.gmane.org>
2017-10-23  1:03       ` Dieter Nützel
2017-10-26 14:10         ` Dieter Nützel [this message]
2017-10-26 17:26           ` Alex Deucher
     [not found]             ` <CADnq5_NzMHaFFrmC3M9hOhiQUnM-xptgKkA-03rLNkJqH8hfQA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-27  2:46               ` Dieter Nützel
  -- strict thread matches above, loose matches on Subject: below --
2017-11-15 19:59 Alex Deucher
2017-11-08 22:52 Alex Deucher
2017-11-02 19:29 Alex Deucher
2017-09-27  1:36 Alex Deucher
     [not found] ` <1506476167-2637-1-git-send-email-alexander.deucher-5C7GfCeVMHo@public.gmane.org>
2017-09-29 13:24   ` 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=cab8fe1180a059f1856c876bd3fe8551@nuetzel-hh.de \
    --to=dieter@nuetzel-hh.de \
    --cc=Rex.Zhu@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).