screen flickering raedon

Bug #1661695 reported by louiedog
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned
Xenial
Triaged
Medium
Unassigned

Bug Description

4.4.0-53 WORKS FINE

4.4.0-62 DOES NOT WORK (screen flickers)

It seems there is a problem with powersafe:

With auto:
echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level

you will see heavy screen flickering on higher display resolutions

With low or high:
echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level or
echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level

there is no screen flickering

And having performance level set to HIGH at all times is not a workaround because it wears out the card. :(

details:

Linux CINNAMON 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

```
    Vendor: X.Org (0x1002)
    Device: AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0) (0x6811)
    Version: 17.1.0
    Accelerated: yes
    Video memory: 2048MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.2
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0)
OpenGL core profile version string: 4.2 (Core Profile) Mesa 17.1.0-devel - padoka PPA
OpenGL core profile shading language version string: 4.20
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

```
---
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: atomi 3734 F.... pulseaudio
 /dev/snd/controlC0: atomi 3734 F.... pulseaudio
 /dev/snd/controlC1: atomi 3734 F.... pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux 18.1
HibernationDevice: RESUME=UUID=30254b0c-14d7-4c0e-9168-a8d492fa027b
InstallationDate: Installed on 2016-12-27 (37 days ago)
InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=41cc7dce-52e8-4b29-9347-60afc0a7d0ed ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-53-generic N/A
 linux-backports-modules-4.4.0-53-generic N/A
 linux-firmware 1.157.6
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: serena
Uname: Linux 4.4.0-53-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/23/2013
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FA
dmi.board.name: GA-78LMT-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1661695

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
louiedog (louiedog) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected serena
description: updated
Revision history for this message
louiedog (louiedog) wrote : CRDA.txt

apport information

Revision history for this message
louiedog (louiedog) wrote : CurrentDmesg.txt

apport information

Revision history for this message
louiedog (louiedog) wrote : IwConfig.txt

apport information

Revision history for this message
louiedog (louiedog) wrote : JournalErrors.txt

apport information

Revision history for this message
louiedog (louiedog) wrote : Lspci.txt

apport information

Revision history for this message
louiedog (louiedog) wrote : Lsusb.txt

apport information

Revision history for this message
louiedog (louiedog) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
louiedog (louiedog) wrote : ProcInterrupts.txt

apport information

Revision history for this message
louiedog (louiedog) wrote : ProcModules.txt

apport information

Revision history for this message
louiedog (louiedog) wrote : PulseList.txt

apport information

Revision history for this message
louiedog (louiedog) wrote : UdevDb.txt

apport information

Revision history for this message
louiedog (louiedog) wrote : WifiSyslog.txt

apport information

louiedog (louiedog)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
louiedog (louiedog) wrote :

Screen flickering is happening in 4.4.0-53 now as well, but much much less often.

I can try earlier versions but this was never an issue in earlier kernels.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc7

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key
louiedog (louiedog)
description: updated
tags: added: kernel-bug-exists-upstream
Revision history for this message
louiedog (louiedog) wrote :

similar bug with the same card https://bugs.freedesktop.org/show_bug.cgi?id=73116

By the way, I tried using amdgpu driver by compiling a daily kernel using Enable amdgpu support for SI/CIK parts and blacklisting radeon and the issue still exists with the amdgpu driver as well.

Revision history for this message
louiedog (louiedog) wrote :

I think a fix for this was committed a few days ago. Possibly http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e8fe3bfd306d376c035c754e6c7d36826a0e3f78

I copied all the new firmware from radeon and amdgpu over to /lib/firmware and rebuilt the latest 4.10 kernel and the issue is gone!

Revision history for this message
louiedog (louiedog) wrote :

@jsalisbur I found the exact commit that fixes this issue for SI cards

in case anyone else comes across this:

https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack/commit/?id=29a73d906bd386839015602c4bd35ef2e3531abc

Revision history for this message
louiedog (louiedog) wrote :

Here are the exact commits that fix this issue for both radeon and amdgpu drivers on 4.10 mainline in case anyone comes across this for SI cards.

https://github.com/torvalds/linux/commit/e894f7ef32deaff134d4c78106a3819eb4ff4136.patch
https://github.com/torvalds/linux/commit/85d2fce605e4625871a4028b36e9c352de2d1ee9.patch

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Changed in linux (Ubuntu Xenial):
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.