All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bug 90340] RADEON "PITCAIRN" displayport output breaks when monitor turned off and on
@ 2015-05-06 13:26 bugzilla-daemon
  2015-05-06 19:44 ` bugzilla-daemon
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: bugzilla-daemon @ 2015-05-06 13:26 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 2146 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 3496 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

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

^ permalink raw reply	[flat|nested] 8+ messages in thread
end of thread, other threads:[~2019-11-19  9:04 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-05-06 13:26 [Bug 90340] RADEON "PITCAIRN" displayport output breaks when monitor turned off and on bugzilla-daemon
2015-05-06 19:44 ` bugzilla-daemon
2015-05-07 10:59 ` bugzilla-daemon
2015-05-07 14:31 ` bugzilla-daemon
2015-05-08  7:05 ` bugzilla-daemon
2015-05-08  7:11 ` bugzilla-daemon
2015-05-08  8:29 ` bugzilla-daemon
2019-11-19  9:04 ` bugzilla-daemon

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.