I found the following link:
https://forum.manjaro.org/t/new-install-amd-fx-6300-wont-wake-from-suspend/39471/10
Suggesting that setting TearFree on may help (RS780L)
However... I wonder if ShadowPrimary did not help.
Section "Device"
Identifier "Radeon"
Driver "radeon"
Option "AccelMethod" "glamor" #legacy "exa"
Option "DRI" "3" #legacy "2"
Option "TearFree" "on"
Option "ColorTiling" "on"
Option "ColorTiling2D" "on"
Option "ShadowPrimary" "on" #only possible with "glamor" AccelMethod
EndSection
Note that it should be in a file /usr/share/X11/xorg.conf.d/20-radeon.conf on
Ubuntu.
And should rename my suggested /etc/X11/xorg.conf to xorg.conf.old.
I might have temporary access to the computer in the next 48h to test
it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1944991
Title:
Resume with glamor cause GPU lockup/screen corruption on Radeon 3100
Graphics" (ChipID = 0x9611)
Status in linux package in Ubuntu:
Incomplete
Bug description:
GPU: ATI Radeon 3100 Graphics (ChipID = 0x9611) (RS780)
GPU Lockup message in dmesg output after resume:
[ 916.000550] radeon 0000:01:05.0: ring 0 stalled for more than 10084msec
[ 916.000569] radeon 0000:01:05.0: GPU lockup (current fence id
0x00000000000020cc last fence id 0x00000000000020d6 on ring 0)
[ 916.516556] radeon 0000:01:05.0: ring 0 stalled for more than 10600msec
[ 916.516569] radeon 0000:01:05.0: GPU lockup (current fence id
0x00000000000020cc last fence id 0x00000000000020d6 on ring 0)
[ 917.024566] radeon 0000:01:05.0: ring 0 stalled for more than 11108msec
[ 917.024575] radeon 0000:01:05.0: GPU lockup (current fence id
0x00000000000020cc last fence id 0x00000000000020d6 on ring 0)
[ 917.536558] radeon 0000:01:05.0: ring 0 stalled for more than 11620msec
[ 917.536570] radeon 0000:01:05.0: GPU lockup (current fence id
0x00000000000020cc last fence id 0x00000000000020d6 on ring 0)
[ 918.048571] radeon 0000:01:05.0: ring 0 stalled for more than 12132msec
[ 918.048580] radeon 0000:01:05.0: GPU lockup (current fence id
0x00000000000020cc last fence id 0x00000000000020d6 on ring 0)
...
[ 935.726783] radeon 0000:01:05.0: GPU softreset: 0x00000019
[ 935.726788] radeon 0000:01:05.0: R_008010_GRBM_STATUS = 0xE57034E0
[ 935.726793] radeon 0000:01:05.0: R_008014_GRBM_STATUS2 = 0x00110103
[ 935.726797] radeon 0000:01:05.0: R_000E50_SRBM_STATUS = 0x20000040
[ 935.726801] radeon 0000:01:05.0: R_008674_CP_STALLED_STAT1 = 0x01000000
[ 935.726805] radeon 0000:01:05.0: R_008678_CP_STALLED_STAT2 = 0x00001002
[ 935.726809] radeon 0000:01:05.0: R_00867C_CP_BUSY_STAT = 0x00028486
[ 935.726813] radeon 0000:01:05.0: R_008680_CP_STAT = 0x80838645
[ 935.726817] radeon 0000:01:05.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 935.779906] radeon 0000:01:05.0: R_008020_GRBM_SOFT_RESET=0x00007FEF
[ 935.779962] radeon 0000:01:05.0: SRBM_SOFT_RESET=0x00000100
[ 935.782061] radeon 0000:01:05.0: R_008010_GRBM_STATUS = 0xA0003030
[ 935.782066] radeon 0000:01:05.0: R_008014_GRBM_STATUS2 = 0x00000003
[ 935.782070] radeon 0000:01:05.0: R_000E50_SRBM_STATUS = 0x20008040
[ 935.782074] radeon 0000:01:05.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 935.782078] radeon 0000:01:05.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[ 935.782081] radeon 0000:01:05.0: R_00867C_CP_BUSY_STAT = 0x00000000
[ 935.782085] radeon 0000:01:05.0: R_008680_CP_STAT = 0x80100000
[ 935.782089] radeon 0000:01:05.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 935.782097] radeon 0000:01:05.0: GPU reset succeeded, trying to resume
Graphics is broken... text hardly readable, interface not responding.
First observed on latest Mint (20.2)... then discovered Peppermint 10 was not
affected.
I believe Peppermint 10 is based on 18.04 and I am unsure why it is not
affected.
I tested with many versions of Ubuntu...
Before 17.04... no problem... but was using EXA acceleration.
17.04 first to use Glamor... screen corruption is not obvious... but dmesg
show
GPU lockup...
17.10 and following is really problematic after resume, but possible to
Ctrl-Alt-F4 to go to a text console and ... sudo reboot.
There is a possibility I missed the exact version as I don't have my notes
near me.
Adding Option "AccelMethod" "EXA"
at the good place in xorg.conf file have fixed the issue.
I am unlikely to have access again to that specific computer in the
future.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
