#783705 xserver-xorg-video-radeon: Weird X wakeup problem since Jessie upgrade

Package:
xserver-xorg-video-radeon
Source:
xserver-xorg-video-ati
Description:
X.Org X server -- AMD/ATI Radeon display driver
Submitter:
Steve McIntyre
Date:
2021-09-22 04:43:23 UTC
Severity:
normal
#783705#5
Date:
2015-04-29 11:45:29 UTC
From:
To:
Hi folks,

I upgrade my main office desktop to Jessie on Monday, and just about
evrrything worked really well - just half a dozen oro so config files
needed merging with new upstream etc. Painless!

However, I'm now seeing a really odd problem with X on my
machine. I've got an AMD graphics card, which Xorg.0.log tells me is a

 RADEON(0): Chipset: "PITCAIRN" (ChipID = 0x6810)

and a DP+ connection to a lovely 27" NEC monitor. It works just fine
when I'm using it, *but* when I leave it overnight and come in the
next morning it doesn't want to wake up properly. I'm locking the
screen with Xscreensaver and then turning off the monitor as I leave.

In the morning, I turn on the screen and I don't get a 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.

Yesterday, I gave up and rebooted after a few minutes - I had work to
do. Today, I started searching for any other reports like this using
my laptop. About ten minutes later while I was doing this
(approximately, wasn't paying massive attention at this point), my
desktop screen suddenly came to life and now it's working OK.

I have no idea of where to even start debugging this. Help!

#783705#10
Date:
2015-05-05 11:40:54 UTC
From:
To:
Similar problem this morning. I've found that using xrandr to disable
and re-enable the DisplayPort output I'm using helps - the display
comes back. Until xrandr segfaults, anyway - see separate bug.

Something weird in the card state, I guess?

#783705#15
Date:
2015-05-05 11:55:16 UTC
From:
To:
Sounds likely.  If this still happens with linux 4.0, can you report
this upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM%2fRadeon
and let us know the bug number?

Thanks,
Julien

#783705#20
Date:
2015-05-05 13:06:40 UTC
From:
To:

If this is a regression, what previous version was working correctly?
Does the problem only happen when you physically power off the
monitor?  Does it come back ok when you let dpms kick in?  How about
when you physically disconnect the monitor from the computer?  Also,
what screensavers are you using?  There may be a problematic GL
screensaver that's causing a GPU lockup.  Can you try forcing a single
known stable screensaver?

Alex

#783705#25
Date:
2015-05-05 13:06:40 UTC
From:
To:

If this is a regression, what previous version was working correctly?
Does the problem only happen when you physically power off the
monitor?  Does it come back ok when you let dpms kick in?  How about
when you physically disconnect the monitor from the computer?  Also,
what screensavers are you using?  There may be a problematic GL
screensaver that's causing a GPU lockup.  Can you try forcing a single
known stable screensaver?

Alex

#783705#30
Date:
2015-05-06 13:12:22 UTC
From:
To:
I was using an up-to-date wheezy installation previously, so that
would be 1:6.14.4-8.

Ah, yes! In fact, it's the act of physically powering off the monitor
that's the problem here. I can reproduce immediately by doing
that. Last night, I locked the screen and left the monitor on and
things were still working fine this morning when I came in.

Pass - I disabled dpms ages ago for unrelated reasons...

I tried that - if I unplugged the cable from the monitor, the monitor
started responding to button presses ok but as soon as I reconnected
it locked up again and still no display.

I just use "bumps" under xscreensaver, and I've had that configured
for years.

#783705#35
Date:
2015-05-06 13:26:40 UTC
From:
To:
OK. New kernel didn't help at all. Bug filed:

https://bugs.freedesktop.org/show_bug.cgi?id=90340

#783705#38
Date:
2015-11-16 19:04:49 UTC
From:
To:
I've seen this bug with Xfce desktop (not related to video driver)
In case of Xfce (xfsettingsd) see bug
https://bugzilla.xfce.org/show_bug.cgi?id=11107

/jkampe

#783705#43
Date:
2021-09-22 04:14:07 UTC
From:
To:
Hello,

Good morning,

We have gone through your samples from a partner and Here is our  Order
List. Please do bear in mind that we are very much in  need of this
order, quote your competitive prices.

Kindly send the Order confirmation.

Your early reply will be much appreciated.

Best Regards,

Maryanah Erwin.

PT FINDORA INTERNUSA

Jln Pahlawan 66 Kec. Arjawinangun

45162 CIREBON West-Java INDONESIA

tel : +62 231 357334

fax: +62 231 357260

email: marketing@findora.com

#783705#46
Date:
2021-09-22 04:14:07 UTC
From:
To:
Hello,

Good morning,

We have gone through your samples from a partner and Here is our  Order
List. Please do bear in mind that we are very much in  need of this
order, quote your competitive prices.

Kindly send the Order confirmation.

Your early reply will be much appreciated.

Best Regards,

Maryanah Erwin.

PT FINDORA INTERNUSA

Jln Pahlawan 66 Kec. Arjawinangun

45162 CIREBON West-Java INDONESIA

tel : +62 231 357334

fax: +62 231 357260

email: marketing@findora.com