https://bugs.freedesktop.org/show_bug.cgi?id=89916
Bug ID: 89916
Summary: DRI PRIME renders only black window
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: towo(a)siduction.org
a have a Lenovo Notebook which contains a FX-7500.
There are 2 graphics devices in:
root@lenovo-nb:/home/towo# lspci | egrep -i "displ|vga"
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Kaveri [Radeon R6/R7 Graphics]
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Jet PRO
[Radeon R5 M230] (rev ff)
The system is using the Kaveri graphics.
towo:lenovo-nb> glxinfo | grep "OpenGL renderer string"
OpenGL renderer string: Gallium 0.4 on AMD KAVERI
towo:lenovo-nb> xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x86 cap: 0xf, Source Output, Sink Output, Source Offload, Sink
Offload crtcs: 4 outputs: 3 associated providers: 1 name:radeon
Provider 1: id: 0x4f cap: 0xf, Source Output, Sink Output, Source Offload, Sink
Offload crtcs: 0 outputs: 0 associated providers: 1 name:radeon
both devices are listed.
xrandr --setprovideroffloadsink 0x4f 0x86
towo:lenovo-nb> DRI_PRIME=1 glxinfo | grep "renderer string"
OpenGL renderer string: Gallium 0.4 on AMD HAINAN
seems to work correct.
DRI_PRIME=1 glxgears
shows only a black window, but the fps are shown in the terminal, i start from.
towo:lenovo-nb> LIBGL_DEBUG=verbose DRI_PRIME=1 glxgears
libGL: screen 0 does not appear to be DRI3 capable
libGL: pci id for fd 4: 1002:6665, driver radeonsi
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/radeonsi_dri.so
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
8793 frames in 5.0 seconds = 1758.569 FPS
doesn't even give any error, but the windows stayes black.
I use xfce 4.12 and have tryed 3 different compositors, with all i get the same
black window. Resizing the windows does not help (that i read in many bug
reports).
kernel is 4.0.0-rc6, xserver is 1.16.4, mesa is 10.6-git and radeon driver is
7.5.0
There are zero errors in the terminal or logfiles.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89858
Bug ID: 89858
Summary: Radeon GPU lockup in Euro Truck Simulator 2
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: xorgbreaker(a)gmail.com
Created attachment 114796
--> https://bugs.freedesktop.org/attachment.cgi?id=114796&action=edit
Radeon GPU lockup
When playing Euro Truck Simulator 2 by using Wine 1.7.39, system freezes and
becomes unusable. I can only use the Magic SysRq "K" and reboot, because VT
switch is not possible after lockup.
My system takes a while to shutdown after that.
In fact, in many games my experience is worst, a bit better when I use an older
kernel, like the LTS 3.14.37.
Software used:
- Linux kernel: 3.19.3-1-ck
- Mesa: 10.5.1
- Radeon driver (xf86-video-ati): 7.5.0
- X Server: 1.17.1
- Distro: Arch Linux x86_64
Hardware used:
- Sapphire Radeon HD 6870
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89815
Bug ID: 89815
Summary: DRI3 and EXA: scrambled output when switching monitors
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: h.judt(a)gmx.at
I am using compiz-0.8. With DRI3 enabled in xorg.conf and AccelMethod EXA, the
output becomes scrambled when switching monitors.
This does not happen with DRI3 off and AccelMethod EXA,
and does not happen with DRI3 on and AccelMethod glamour.
There seems no proper way to restore functionality except killing compiz
(leaving a black screen) and starting another window manager, like xfwm4. After
that, launching compiz again is not possible, I have to restart the X server.
Using xf86-video-ati git master (391900a670addec39515f924265bfa9f8bfa9ec0).
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Cayman PRO [Radeon HD 6950] (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD
6950]
Flags: bus master, fast devsel, latency 0, IRQ 25
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at f7e20000 (64-bit, non-prefetchable) [size=128K]
I/O ports at e000 [size=256]
Expansion ROM at f7e00000 [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
Capabilities: [150] Advanced Error Reporting
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89801
Bug ID: 89801
Summary: [drm:0xffffffff8155bb10] *ERROR* si_set_sw_state
failed
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: anhermann(a)gmx.net
Created attachment 114676
--> https://bugs.freedesktop.org/attachment.cgi?id=114676&action=edit
dmesg output
Hi,
I see this message in dmesg after each resume from S3 suspend state. My card is
a R9 270x. Prior to kernel 3.19.3, i randomly wasn't able to suspend
the machine at all. However, that seems to be fixed now after upgrading to
3.19.3.
The only issue remaining is the mentioned error message. I have to admit that
the machine works perfectly, Xorg.log shows no errors, everything seems OK, so
thank you very much for the important fixes that went into 3.19.3.
But I wonder what this error message means. DPM related? I tested the switching
of performance levels via debugfs and that seems to work too but maybe not
correct???
I attached the dmesg showing the error message, let me know if and how I can
help you with some for debug information.
Thanks a lot
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89713
Bug ID: 89713
Summary: [radeon]GPU lockup in World of Tanks with gallium nine
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: pontostroy(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 114523
--> https://bugs.freedesktop.org/attachment.cgi?id=114523&action=edit
dmesg
Afrer same time (10-20 min) objects in the game begin to disappear and if i do
not close the application for 10-15 seconds I get gpuhang.
I tried all R600_DEBUG options but nothing helped
4.0.0-rc3(debug kernel)
Mesa\libdrm\ddx\x-server - git 2015.03.20-22
Radeon Hd 7790
Intel i5 3330
Opensuse factory
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89536
Bug ID: 89536
Summary: GPU lockup and kernel OOPS when using PRIME
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: rafael.ristovski(a)gmail.com
Created attachment 114225
--> https://bugs.freedesktop.org/attachment.cgi?id=114225&action=edit
Two of the kernel hangs, note one is an OOPS, while the other is not, I was
able to shut down the machine normally after the first OOPS as the kernel was
still responsive to power button events.
When running OpenGL applications with PRIME, the screen freezes and a kernel
OOPS is generated. This seems to happen either when the application starts, or
the window of the application is re-drawn (moving workspaces,
minimizing/maximizing) Crashes seem to be inconsistent as sometimes the kernel
just freezes and no OOPS is generated.
OS Details:
Archlinux with kernel 3.19.1-1
xorg-server 1.17.1-3
xf86-video-intel 2.99.917-4
xf86-video-ati 1:7.5.0-2
libdrm 2.4.59-1
Below is an attached kernel log with _TWO_ separate kernel hang, both caused by
running an OpenGL application with PRIME.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89479
Bug ID: 89479
Summary: HDMI audio won't pass ac3 through another device
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: linux(a)cmadams.net
I have an AMD E-350 system (Radeon HD6310). When I connect it directly to my
receiver and play a file with AC3 audio, the receiver properly switches over to
Dolby Digital decoding. However, when I connect the HDMI to another device's
pass-through (Vizio TV, Xbox One), the receiver stays in stereo mode and I get
garbage audio. Other devices can send Dolby Digital through (e.g. I tried a
TiVo Roamio through the Vizio TV), so I know it can be done.
I'm guessing there's some bit of HDMI handshake not happening when the Radeon
tries to switch modes and is connected to another device, but I don't know how
to debug that. Please let me know what I can do to figure this out.
I'm testing this with a trailer downloaded from hdtrailers.net, playing with
either XBMC or VLC.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89405
Bug ID: 89405
Summary: radeon: *ERROR* invalid ioctl running weston-launch
while X is running
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: fosero(a)gmail.com
Created attachment 113938
--> https://bugs.freedesktop.org/attachment.cgi?id=113938&action=edit
weston-launch -u as root
If I try to start a weston instance by using weston-launch, while gdm on X is
running I get the following kernel message :
[di mrt 3 09:39:01 2015] [drm:radeon_cp_getparam_kms] *ERROR* invalid ioctl
with kms radeon_cp_getparam_kms
[di mrt 3 09:39:01 2015] [drm:radeon_engine_reset_kms] *ERROR* invalid ioctl
with kms radeon_engine_reset_kms
weston-launch refuses to run, attached a log of its debug output.
kernel - 3.19.0
libdrm - 2.4.59
RS780
weston/wayland 1.7
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89374
Bug ID: 89374
Summary: Firefox smooth scrolling isn't smooth
Product: DRI
Version: XOrg git
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: sunweb(a)hotmail.ru
Kubuntu 14.04 x64, HD5770
glxinfo |grep Open
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD JUNIPER
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.2
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.3.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
Firefox has an option of smooth scrolling(Preferences -> General -> Use smooth
scrolling). However it doesn't work on OSS drivers for my card. It does work on
Intel ones and closed source though.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89275
Bug ID: 89275
Summary: PC sometimes hangs on suspend
Product: Mesa
Version: 10.3
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: sunweb(a)hotmail.ru
QA Contact: dri-devel(a)lists.freedesktop.org
Kubuntu 14.04.2, Radeon HD5770.
When i am going on suspend mode(RAM) screen goes black and then PC might or
might not go into this mode. Sometimes it just hangs on black screen part and
thats it. It happened to me with all of the previous drivers(and mesa 10.1) but
i've seen once back then so i thought its a rare bug.
Filled ram or not, i don't what may be the cause and where to look for errors
to post here, so if you'll tell me where to look i'll post them.
--
You are receiving this mail because:
You are the assignee for the bug.