From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 90340] RADEON "PITCAIRN" displayport output breaks when monitor turned off and on Date: Wed, 06 May 2015 13:26:11 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0064673417==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 96F456E689 for ; Wed, 6 May 2015 06:26:11 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0064673417== Content-Type: multipart/alternative; boundary="1430918771.b877dc50.13230"; charset="UTF-8" --1430918771.b877dc50.13230 Date: Wed, 6 May 2015 13:26:11 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=90340 Bug ID: 90340 Summary: RADEON "PITCAIRN" displayport output breaks when monitor turned off and on Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel@lists.freedesktop.org Reporter: steve@einval.com As initially reporte in Debian at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783705 I'm running Debian Jessie (3.16.x kernel) on a machine with a Pitcairn-based video adapter and an NEC Multisync EA274WMi 27" monitor, connected via DisplayPort. I've also tried upgrading to the 4.0 kernel and I see exactly the same symptoms. If I turn the monitor off and then on again (as I was doing overnight), I get no display at all. I've wiggled the mouse, hit numlock on the keybard (the numlock led illuminates fine), etc., but no display. I've seen this kind of thing happen in the past on some machines, so I switch to VT1 and back to see if that helps. Still no display at all, either on console or under X. I log in remotely and I can see that the Xorg.0.log file has been updated with mode lines for the monitor, suggesting things have just woken up fine. But still no display. Here's the really weird thing: at this point, the monitor has basically locked up. It won't respond to the power/input/menu butttons at all, and is still showing the blue LED that says "I have signal" rather than switching to the amber "no signal" warning. Therefore, I can only assume there's a problem here with some weird invalid DP signal being produced. I've carried on playing with this. If I log in from another machine and run xrandr, I can see the display details of the monitor just fine. If I use xrandr to turn the display off and then on again: xrandr --output DisplayPort-0 --off xrandr --output DisplayPort-0 2560x1440 then things start working again. -- You are receiving this mail because: You are the assignee for the bug. --1430918771.b877dc50.13230 Date: Wed, 6 May 2015 13:26:11 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"
Bug ID 90340
Summary RADEON "PITCAIRN" displayport output breaks when monitor turned off and on
Product DRI
Version XOrg git
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component DRM/Radeon
Assignee dri-devel@lists.freedesktop.org
Reporter steve@einval.com 

As initially reporte in Debian at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783705

I'm running Debian Jessie (3.16.x kernel) on a machine with a Pitcairn-based
video adapter and an NEC Multisync EA274WMi 27" monitor, connected via
DisplayPort.

I've also tried upgrading to the 4.0 kernel and I see exactly the same
symptoms.

If I turn the monitor off and then on again (as I was doing overnight), I get
no display at all. 

I've wiggled the mouse, hit numlock on the keybard (the numlock
led illuminates fine), etc., but no display. I've seen this kind of
thing happen in the past on some machines, so I switch to VT1 and back
to see if that helps. Still no display at all, either on console or
under X. I log in remotely and I can see that the Xorg.0.log file has
been updated with mode lines for the monitor, suggesting things have
just woken up fine. But still no display.

Here's the really weird thing: at this point, the monitor has
basically locked up. It won't respond to the power/input/menu butttons
at all, and is still showing the blue LED that says "I have signal"
rather than switching to the amber "no signal" warning. Therefore, I
can only assume there's a problem here with some weird invalid DP
signal being produced.

I've carried on playing with this. If I log in from another machine and run
xrandr, I can see the display details of the monitor just fine. If I use xrandr
to turn the display off and then on again:

xrandr --output DisplayPort-0 --off
xrandr --output DisplayPort-0 2560x1440

then things start working again.

You are receiving this mail because:
  • You are the assignee for the bug.
--1430918771.b877dc50.13230-- --===============0064673417== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0064673417==--