https://bugs.freedesktop.org/show_bug.cgi?id=94933
Bug ID: 94933
Summary: [RV610] Freeze when turning on an external monitor
after resume from suspend
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter:…
[View More] nicolamori(a)aol.com
I have a laptop with a Mobility Radeon HD3470 (RV610) and Plasma 5.6.2 as
desktop environment. After suspending to RAM and resuming, I experience a
system freeze when trying to switch to a dual monitor setup using an external
monitor connected to the VGA output. The dual monitor can be turned on without
problems before the suspend/resume cycle.
I don't know which logs/information could be useful to diagnose the problem, so
I will provide it on demand. Thanks.
System details
--------------
VGA: Mobility Radeon HD3470 (RV610)
OS: ArchLinux 64 bit, kernel 4.4.7, xf86-video-ati 7.7.0
Desktop: Plasma 5.6.2 (with KF5 5.21 and Qt 5.6.0)
Steps to reproduce
------------------
- Start the system with only the laptop panel turned on
- Suspend to RAM and then resume
- Connect an external monitor
- Enable the external monitor with xrandr or with the KCM module (System
settings -> Display and Monitor -> Display configuration)
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=94903
Bug ID: 94903
Summary: Tahiti and Hawaii (without amdgpu support) skips
vblanks on wayland (weston and others) on some
displays.
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/radeonsi
…
[View More]Assignee: dri-devel(a)lists.freedesktop.org
Reporter: johngaltfirstrun(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
When running weston on this hardware with Shimian QHD270 displays, vblanks are
skipped resulting in stuttering video playback on any framerate other than
60fps (with multiple players and vo including opengl and wayland (shm)).
System:
Mesa: git
linux: 4.4, 4.5, 4.6 from a drm-next-wip branch
wayland: git
weston: git
A few notes:
- This doesn't occur when using amdgpu (for instance building with hawaii
amdgpu support.
- This bug goes back as far as a year, and another user verified they had this
issue on a radeonsi card with a specific monitor.
- When utilizing amdgpu, the EDID is correctly read from these monitors.
Without, the EDID read fails. I've written the EDID to a file in /lib/firmware/
and successfully loaded with no change however.
- Outside of video playback, there are no vblank skips. It was explained that
each application affects the entire compositor.
- No change on video size. The issue is apparent (with no discernible change)
on non-60fps 360p youtube videos on up to high bitrate x265 4K tv shows.
- By increasing repaint-window, I'm able to get consistent playback and no
vblank skips. However I do run into other issues with it, showing it's clearly
not a real solution for wayland support on radeon.
- During video playback, weston-presentation-shm shows the missing vblanks
just as a timeline does (so including weston-presentation-shm log for
readability instead).
weston-presentation-shm log with video playback at beginning:
https://bpaste.net/show/f8c9b910ddc1. When vblanks are no longer skipped, the
video playback has stopped.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=94708
Bug ID: 94708
Summary: Open source radeon drivers not working properly with
Radeon HD 8550M
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: …
[View More]markotikvic(a)gmail.com
Dear Maintainer,
I have a Lenovo laptop with hybrid AMD/Intel graphics cards. I would like to
use the discrete Radeon card for heavy rendering operations such as game
development and gaming.
Output of xrandr --listproviders:
Provider 0: id: 0x76 cap: 0xb, Source Output, Sink Output, Sink Offload
crtcs: 3 outputs: 4 associated providers: 1 name:Intel
Provider 1: id: 0x4f cap: 0xf, Source Output, Sink Output, Source Offload,
Sink Offload crtcs: 0 outputs: 0 associated providers: 1 name:radeon
But I get lower fps when I run games with discrete GPU:
xrandr --setprovideroffloadsink radeon Intel
env DRI_PRIME=1 <game> <- results in barely 20 fps for Dota 2
than if I run them with integrated Intel's card:
env DRI_PRIME=0 <game> <- results in 50-60 fps for Dota 2
The output of DRI_PRIME=0 glxinfo | grep 'OpenGL renderer' is:
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
and the ouput of DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' is:
OpenGL renderer string: Gallium 0.4 on AMD HAINAN
>From dmesg I can see this error occuring after starting the game with
DRI_PRIME=1 flag set:
[ 1406.107887] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[ 1406.107892] [drm] PCIE gen 2 link speeds already enabled
[ 1406.110997] [drm] PCIE GART of 1024M enabled (table at
0x0000000000040000).
[ 1406.111090] radeon 0000:0a:00.0: WB enabled
[ 1406.111093] radeon 0000:0a:00.0: fence driver on ring 0 use gpu addr
0x0000000080000c00 and cpu addr 0xffff88009ae5bc00
[ 1406.111094] radeon 0000:0a:00.0: fence driver on ring 1 use gpu addr
0x0000000080000c04 and cpu addr 0xffff88009ae5bc04
[ 1406.111096] radeon 0000:0a:00.0: fence driver on ring 2 use gpu addr
0x0000000080000c08 and cpu addr 0xffff88009ae5bc08
[ 1406.111097] radeon 0000:0a:00.0: fence driver on ring 3 use gpu addr
0x0000000080000c0c and cpu addr 0xffff88009ae5bc0c
[ 1406.111098] radeon 0000:0a:00.0: fence driver on ring 4 use gpu addr
0x0000000080000c10 and cpu addr 0xffff88009ae5bc10
[ 1406.305207] [drm] ring test on 0 succeeded in 1 usecs
[ 1406.305213] [drm] ring test on 1 succeeded in 1 usecs
[ 1406.305218] [drm] ring test on 2 succeeded in 1 usecs
[ 1406.305226] [drm] ring test on 3 succeeded in 4 usecs
[ 1406.305233] [drm] ring test on 4 succeeded in 4 usecs
[ 1406.305294] [drm] ib test on ring 0 succeeded in 0 usecs
[ 1406.305347] [drm] ib test on ring 1 succeeded in 0 usecs
[ 1406.305399] [drm] ib test on ring 2 succeeded in 0 usecs
[ 1406.305412] [drm] ib test on ring 3 succeeded in 0 usecs
[ 1406.305424] [drm] ib test on ring 4 succeeded in 0 usecs
[ 1406.305677] [drm:si_dpm_set_power_state] *ERROR* si_upload_sw_state
failed
I know the GPU is being used because the vgaswitcheroo shows it as DynPwr when
I run apps with it.
What I would expect to see is performance AT LEAST as good as integrated GPU,
instead I get a very bad performance. The poor perfomance is also observable
when I run Unity 3D editor (with DRI_PRIME=1) in terms of screen tearing and
system freezing. I also tried running the game with vblank_mode=0 option but it
had no effect on performance.
The scenario is similar with any app I run with DRI_PRIME=1 and it's mostly
noticeable with screen tearing.
Kernel version: Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1
(2016-03-06) x86_64 GNU/Linux
I have searched tons of forum threads and websites and I couldn't find a
solution (there were some similar open and unresolved threads but nothing
useful), so I turn to you for some hardcore professional help. Is there
anything I can try to fix this? Oh, I also tried using LXDE desktop but it made
no difference, the problems were the same. Let me know if you need other logs
and outputs in order to figure this thing out. I am more than happy to help.
Thank you in advance,
Marko.
P.S. Forgive me if I've post this to the wrong package thread but it definitely
has something to do with DRI/radeon/xserver package(s).
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=94502
Bug ID: 94502
Summary: R9-270 has no video output when underclocked
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: maweki(a)gmail.com
I have a Radeon R9-270 and I …
[View More]am running Fedora 23 with the default OpenSource
drivers supplied with the repository.
Yesterday I did an Update from Kernel 4.3.3-300 to 4.4.3-300 and I started
seeing some issues. When I do nothing for about 12 seconds the screens (dual
head) turn blank. Moving the mouse makes the screen go back on again. Sometimes
the login-screen of the gnome-shell or chrome are frozen but the system as a
whole seems fine.
During normal operations /sys/kernel/debug/dri/0/radeon_pm_info is the
following:
power level 0 sclk: 30000 mclk: 120000 vddc: 950 vddci: 1000 pcie gen: 2
When the screen is still for a bit (exactly when it turns blank) the output is
power level 0 sclk: 30000 mclk: 15000 vddc: 900 vddci: 850 pcie gen: 2
So apparently, when the video card is clocked down, the output is deactivated.
My current "workaround" is running videos on the side - not an ideal solution.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=94484
Bug ID: 94484
Summary: Kernel BUG with latest radeon driver
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: tyler.brock(a)gmail.com
Created attachment 122213
--> …
[View More]https://bugs.freedesktop.org/attachment.cgi?id=122213&action=edit
journalctl output when radeon driver crashes
Hey everyone, I'm running Linux 4.4.5 and Radeon driver xf86-video-ati 1:7.6.1
on wayland.
I had no problems about a week ago but since using this version I frequently go
to wake up my display by hitting a key on keyboard or moving the mouse and find
that my computer has completely crashed (requiring a hard reboot).
I've included the relevant output from journalctl.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=93895
Bug ID: 93895
Summary: GPU lockup on AMD A4-3400 APU when starting X server
on opensource drivers. (works fine with fglrx)
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.…
[View More]freedesktop.org
Reporter: azari4096(a)gmail.com
I've had this lockup on this machine for the past few years, across several
different kernel versions, different distributions, etc. Booting with KMS works
fine, but the second a graphical environment starts (whether X or
wayland-based), it locks up.
Booting Ubuntu with user-space mode-setting works, and then I can install FGLRX
from there and everything works fine. After speaking with airlied on IRC, they
suggested it could be a workaround that AMD has put into FGLRX that never made
it into the opensource drivers, and that AMD might have to look into it.
CPU/GPU : A4-3400
Motherboard : GA-A75M-D2H (
http://www.gigabyte.com/products/product-page.aspx?pid=3930#ov )
journalctl log of the lockup:
------------------------------------------------------------
Jan 27 18:28:32 miku dbus-daemon[374]: Successfully activated service
'org.freedesktop.systemd1'
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: ring 0 stalled for more
than 10000msec
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU lockup (current fence
id 0x0000000000000001 last fence id 0x0000000000000003 on ring 0)
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: Saved 55 dwords of
commands on ring 0.
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU softreset: 0x00000009
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS
= 0xB1403828
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE0
= 0x28000007
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE1
= 0x00000007
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS
= 0x20000840
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS2
= 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
R_008674_CP_STALLED_STAT1 = 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
R_008678_CP_STALLED_STAT2 = 0x40000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00867C_CP_BUSY_STAT
= 0x00008000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008680_CP_STAT
= 0x80228643
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00D034_DMA_STATUS_REG
= 0x44C83D57
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
GRBM_SOFT_RESET=0x00007F6B
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
SRBM_SOFT_RESET=0x00000100
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS
= 0x00003828
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE0
= 0x00000007
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE1
= 0x00000007
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS
= 0x20000040
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS2
= 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
R_008674_CP_STALLED_STAT1 = 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
R_008678_CP_STALLED_STAT2 = 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00867C_CP_BUSY_STAT
= 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008680_CP_STAT
= 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00D034_DMA_STATUS_REG
= 0x44C83D57
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU reset succeeded,
trying to resume
Jan 27 18:28:42 miku kernel: [drm] Found smc ucode version: 0x00011100
Jan 27 18:28:42 miku kernel: [drm] PCIE GART of 1024M enabled (table at
0x0000000000274000).
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: WB enabled
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 0
use gpu addr 0x0000000020000c00 and cpu addr 0xffff8800c613fc00
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 3
use gpu addr 0x0000000020000c0c and cpu addr 0xffff8800c613fc0c
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 5
use gpu addr 0x0000000000072118 and cpu addr 0xffffc90002432118
Jan 27 18:28:42 miku kernel: [drm] ring test on 0 succeeded in 1 usecs
Jan 27 18:28:42 miku kernel: [drm] ring test on 3 succeeded in 3 usecs
Jan 27 18:28:42 miku kernel: [drm] ring test on 5 succeeded in 1 usecs
Jan 27 18:28:42 miku kernel: [drm] UVD initialized successfully.
Jan 27 18:28:52 miku kernel: radeon 0000:00:01.0: ring 0 stalled for more
than 10370msec
Jan 27 18:28:52 miku kernel: radeon 0000:00:01.0: GPU lockup (current fence
id 0x0000000000000002 last fence id 0x0000000000000004 on ring 0)
Jan 27 18:28:52 miku kernel: [drm:r600_ib_test [radeon]] *ERROR* radeon:
fence wait failed (-35).
Jan 27 18:28:52 miku kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR*
radeon: failed testing IB on GFX ring (-35).
Jan 27 18:29:22 miku systemd[1]: Started Getty on tty2.
------------------------------------------------------------
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=93879
Bug ID: 93879
Summary: kernel 4.4.0 causes application lockup and unusable
interfaces with radeon hardware
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
…
[View More]Reporter: jimmy(a)boombatower.com
Created attachment 121320
--> https://bugs.freedesktop.org/attachment.cgi?id=121320&action=edit
sh -c "cat /proc/version; ./scripts/ver_linux; cat /proc/cpuinfo; cat
/proc/modules; cat /proc/ioports; cat /proc/iomem; lspci -vvv; cat
/proc/scsi/scsi" > env_info
While running Plasma 5 on 4.4.0 the following occurs periodically:
- chromium locks up
- plasma desktop locks up
- unable to enter password on plasma lock screen
A trigger for locking chromium up seems to be to resize the window by dragging
to screen edges (top to fullscreen, left to tack up left half of screen, etc).
Otherwise, it also seems to somewhat randomly freeze over time.
Reverting to 4.3.x resolves the issues.
Environment
-----------
Distro: openSUSE Tumbleweed (20160121) (x86_64)
Kernel version: 4.4.0-1.2 (works on <= 4.3.3-6)
OpenGL renderer string: Gallium 0.4 on AMD TAHITI (DRM 2.43.0, LLVM 3.7.0)
OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.1.0
Xorg version: 7.6_1.18.0-5.2
xf86-video-ati version: 7.6.1-1.2
DRI3 enabled
Hardware: Radeon HD 7970 ghz
output from kernel bug reporting guide attached
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=93819
Bug ID: 93819
Summary: R9 390: [drm:radeon_vce_ring_test] *ERROR* ring 6 test
failed after resume from hibernate
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: h.…
[View More]judt(a)gmx.at
Created attachment 121201
--> https://bugs.freedesktop.org/attachment.cgi?id=121201&action=edit
dmesg1
It does not happen always, but usually after a few hibernate/resume cycles (2
or 3, sometimes earlier). The following messages can be found in dmesg (see
attachment for full output).
[ 1001.941216] [drm] ring test on 0 succeeded in 0 usecs
[ 1001.941331] [drm] ring test on 1 succeeded in 0 usecs
[ 1001.941370] [drm] ring test on 2 succeeded in 0 usecs
[ 1001.941565] [drm] ring test on 3 succeeded in 0 usecs
[ 1001.941571] [drm] ring test on 4 succeeded in 0 usecs
[ 1001.967662] [drm] ring test on 5 succeeded in 0 usecs
[ 1001.967696] [drm] UVD initialized successfully.
[ 1002.249117] [drm:radeon_vce_ring_test] *ERROR* radeon: ring 6 test failed]
[ 1002.249139] [drm] ib test on ring 0 succeeded in 0 usecs
[ 1002.749193] [drm] ib test on ring 1 succeeded in 0 usecs
[ 1002.749221] [drm] ib test on ring 2 succeeded in 0 usecs
[ 1002.749304] [drm] ib test on ring 3 succeeded in 0 usecs
[ 1002.749354] [drm] ib test on ring 4 succeeded in 0 usecs
[ 1003.269160] [drm] ib test on ring 5 succeeded
[ 1013.788806] radeon 0000:01:00.0: ring 7 stalled for more than 10000msec
[ 1013.788809] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000000008 last fence id 0x000000000000000a on ring 7)
[ 1013.788868] [drm:radeon_vce_ib_test] *ERROR* radeon: fence wait failed
(-35).
[ 1013.788874] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
ring 7 (-35).
After that, if the machine hibernates and resumes once again, additional errors
will be printed and the X session becomes unusable (only the cursor blinking on
the terminal). I will attach the dmesg of this too, though it might be less
interesting.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]