https://bugs.freedesktop.org/show_bug.cgi?id=104963
Bug ID: 104963
Summary: MSI MoBo A88XM-E35 GPU Trinity A8-5600K (Aruba
HD7560D) Boot loop without radeon.dpm=0
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: f0rhum(a)free.fr
Hi
I was driven here by Ubuntu team :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746357
Only nomodeset and radeon.dpm=0 allow boot. Issue is here from kernel 3.13 to
4.15.1
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=104738
Bug ID: 104738
Summary: Radeon HD 6970M/6990M crash on iMac on boot - only
nomodeset helps
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: hansmatros76(a)gmail.com
Created attachment 136905
--> https://bugs.freedesktop.org/attachment.cgi?id=136905&action=edit
dmesg
Dear Developers!
I have this bug on different Linux kernels. Only with 4.15.0-041500rc8 i am
able to boot, but there is no hardware acceleration.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743427
If you need more informations please let me know.
Best regards,
Hans
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=104508
Bug ID: 104508
Summary: Unable to set "IT Content" bit for HDMI and
DisplayPort
Product: DRI
Version: unspecified
Hardware: All
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: nw9165-3201(a)yahoo.com
Hi,
apparently the Intel HD Graphics driver for Windows has a "IT Content" option
that can be either enabled or disabled, see following screenshot for example:
https://www.howtogeek.com/wp-content/uploads/2016/12/img_5855c293ac26d.jpg
According to a post on the AVS Forum, enabling "IT Content" does the following:
http://www.avsforum.com/forum/26-home-theater-computers/1477460-theory-abou…
> HDMI specs "IT Content" flag is set On in video stream.
>
> CEA-861:
> "In IT applications (e.g. involving bit mapped text),
> each pixel in the source’s frame buffer is most clearly
> displayed if it is directly mapped to a light-emitting pixel
> on the display device - such that adjacent pixels are
> completely independent and do not interact.
> The IT content bit indicates when picture content is
> composed according to common IT practice (i.e. without
> regard to Nyquist criterion) and is unsuitable for
> analog reconstruction or filtering. When the IT content bit
> is set to 1, downstream processors should pass
> pixel data unfiltered and without analog reconstruction."
Apparently there is no option for it on the RADEON Linux driver.
Can you please add an option to the RADEON Linux driver which allows to enable
the "IT Content" bit?
Regards
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=104053
Bug ID: 104053
Summary: DDX opcode causes black screen on radeon R730
Product: DRI
Version: XOrg git
Hardware: All
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: lodgerz(a)gmail.com
Hi,
i have a problem with retroarch+xmb on ArchLinux32bit: when i run it i have
black screen, monitor led blinking and i must reset pc.
This is final output error of retroarch:
[INFO] [GL]: VSync => on
[INFO] [GLX]: glXSwapIntervalEXT(1)
r300 VP: Compiler error:
Vertex program has too many instructions
Using a dummy shader instead.
r300 FP: Compiler Error:
compiler/r300_fragprog_emit.c::translate_rgb_opcode(): translate_rgb_opcode:
Unknown opcode DDX
Using a dummy shader instead.
If i run it with "LIBGL_ALWAYS_SOFTWARE=1 retroarch" it works but is very slow
(games run at 30fps).
I use xf86-video-ati driver and mesa.
More info: http://dpaste.com/39C6SQF
Retroarch devolopers advised me to ask here.
--------------------------------
$ glxinfo | grep renderer
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: ATI RV370
--------------------------------
$ LIBGL_ALWAYS_SOFTWARE=1 glxinfo | grep renderer
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: llvmpipe (LLVM 5.0, 128 bits)
--------------------------------
$ lsmod|grep -i radeon
radeon 1343488 2
i2c_algo_bit 16384 1 radeon
drm_kms_helper 126976 1 radeon
ttm 69632 1 radeon
drm 258048 5 radeon,ttm,drm_kms_helper
--------------------------------
$ lspci|grep -i vga
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370
[Radeon X300/X550/X1050 Series]
--------------------------------
$ pacman -Q|grep xf86-video
xf86-video-ati 1:7.10.0-1
xf86-video-fbdev 0.4.4+12+ge0bce0d-1
xf86-video-vesa 2.3.4-4
--------------------------------
$ pacman -Q|grep mesa
mesa 17.2.5-1
mesa-demos 8.3.0-4
mesa-vdpau 17.2.5-1
--------------------------------
$ uname -r
4.13.12-1-ARCH
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=103403
Bug ID: 103403
Summary: something going on across the gpu DAC and monitor.
Product: DRI
Version: XOrg git
Hardware: x86 (IA32)
URL: https://forum.manjaro.org/t/ati-graphics-card-drivers-
how-to/32784/67
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: korbs(a)gmx.com
Created attachment 134989
--> https://bugs.freedesktop.org/attachment.cgi?id=134989&action=edit
specs included
It’s not tearing, it’s not corruption in the graphics rendering.
On Manjaro KDE
However, I have noticed an annoying thing with the display and I am almost
certain it is related to the drivers I am using.
A straight line that goes across the screen,
I have noticed sth - when the screen dims, saving energy option allows that,
the lines are not visible at all.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=102800
Bug ID: 102800
Summary: DRI_PRIME regression- radeon: Failed to allocate
virtual address for buffer
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: higuita(a)gmx.net
Using a ubuntu 17.04 with a kernel 4.13.2, mesa 1.3-git and libdrm 2.4.83 on a
lenovo thinkpad S440 with a intel haswell and a radeon HD8670M/8690M
doing this commands i get a error:
+ xrandr --setprovideroffloadsink 0x3f 0x66
+ DRI_PRIME=1
+ glxgears
radeon: Failed to allocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x0000000000800000
radeon: Failed to deallocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: va : 0x800000
radeon: Failed to allocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x0000000000800000
radeon: Failed to deallocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: va : 0x800000
radeonsi: Failed to create a context.
radeon: Failed to allocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x0000000000800000
radeon: Failed to deallocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: va : 0x800000
radeon: Failed to allocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x0000000000800000
radeon: Failed to deallocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: va : 0x800000
radeonsi: Failed to create a context.
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 31
Current serial number in output stream: 33
In the dmesg, i can see this:
[ 1059.004670] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for
more than 5secs aborting
[ 1059.004693] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck
executing 746C (len 237, WS 0, PS 4) @ 0x747A
[ 1059.004703] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck
executing 6E04 (len 74, WS 0, PS 8) @ 0x6E39
[ 1059.012106] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[ 1059.012110] [drm] PCIE gen 2 link speeds already enabled
[ 1059.448659] [UFW ALLOW] IN= OUT=wlan0 SRC=10.42.42.80 DST=140.172.138.79
LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=44245 DF PROTO=TCP SPT=50408 DPT=80
WINDOW=30498 RES=0x00 ACK FIN URGP=0
[ 1059.476638] radeon 0000:06:00.0: Wait for MC idle timedout !
[ 1059.708499] radeon 0000:06:00.0: Wait for MC idle timedout !
[ 1059.714600] [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000).
[ 1059.714727] radeon 0000:06:00.0: WB enabled
[ 1059.714730] radeon 0000:06:00.0: fence driver on ring 0 use gpu addr
0x0000000080000c00 and cpu addr 0xffff8c2c59b12c00
[ 1059.714731] radeon 0000:06:00.0: fence driver on ring 1 use gpu addr
0x0000000080000c04 and cpu addr 0xffff8c2c59b12c04
[ 1059.714732] radeon 0000:06:00.0: fence driver on ring 2 use gpu addr
0x0000000080000c08 and cpu addr 0xffff8c2c59b12c08
[ 1059.714732] radeon 0000:06:00.0: fence driver on ring 3 use gpu addr
0x0000000080000c0c and cpu addr 0xffff8c2c59b12c0c
[ 1059.714733] radeon 0000:06:00.0: fence driver on ring 4 use gpu addr
0x0000000080000c10 and cpu addr 0xffff8c2c59b12c10
[ 1060.424258] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed
(scratch(0x850C)=0xCAFEDEAD)
[ 1060.424283] [drm:si_resume [radeon]] *ERROR* si startup failed on resume
All this setup worked fine in a previous kernel versions, IIRC, 4.11 and below
and started to fail in 4.12 and above
I also notice that the dedicated card switch fron DynOff to DynPwr in
/sys/kernel/debug/vgaswitcheroo/switch for a few seconds when trying to run the
glxgears
Finally, If i boot the system with radeon.runpm=1, it works
Let me know if you need more logs
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=102659
Bug ID: 102659
Summary: Radeon 7970M Lockup
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: vilsol2000(a)gmail.com
Created attachment 134160
--> https://bugs.freedesktop.org/attachment.cgi?id=134160&action=edit
DMESG Log
I am experiencing full GPU lockup when running anything on the GPU (using the
DRI_PRIME=1 flag).
No matter how demanding is whatever I am testing, after ~3min it will lock up
the GPU and freeze.
I am running on 4.10.0-34-lowlatency kernel with everything else up to date.
(same error on generic kernel).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=102599
Bug ID: 102599
Summary: Window decoration not being painted with DRI3 and
Compiz-Reloaded+Emerald
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: freedesktop.org(a)styxxx.de
Created attachment 134059
--> https://bugs.freedesktop.org/attachment.cgi?id=134059&action=edit
Xorg.0.log with DRI3
Hi,
I originally filed a bug report at the compiz-reloaded project. You can read
about the issue and the original conversation here:
https://github.com/compiz-reloaded/compiz/issues/82
When using Compiz-Reloaded + Emerald and DRI3 the window decoration is not
being painted correctly: It's just a plain white border. You can still click
the insivible buttons or resize the window. So it's an issue with rendering the
window border. No error messages and no log entries are produced.
The problem doesn't occur after I switched to DRI2.
Thank you :)
Debian testing/stretch, 4.12.0-1-amd64 #1 SMP Debian 4.12.6-1 (2017-08-12)
x86_64 GNU/Linux
glxinfo | grep renderer:
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Gallium 0.4 on AMD PALM (DRM 2.50.0 / 4.12.0-1-amd64,
LLVM 3.9.1)
Installed packages:
$ dpkg -l | grep xserver
ii x11-xserver-utils 7.7+7+b1
amd64 X server utilities
ii xserver-common 2:1.19.3-2
all common files used by various X servers
ii xserver-xephyr 2:1.19.3-2
amd64 nested X server
ii xserver-xorg 1:7.7+19
amd64 X.Org X server
ii xserver-xorg-core 2:1.19.3-2
amd64 Xorg X server - core server
ii xserver-xorg-input-evdev 1:2.10.5-1
amd64 X.Org X server -- evdev input driver
ii xserver-xorg-input-mouse
1:1.9.2-1+b1 amd64 X.Org X server -- mouse
input driver
ii xserver-xorg-input-synaptics 1.9.0-1+b1
amd64 Synaptics TouchPad driver for X.Org
server
ii xserver-xorg-input-wacom
0.34.99.1-1 amd64 X.Org X server -- Wacom
input driver
ii xserver-xorg-legacy 2:1.19.3-2
amd64 setuid root Xorg server wrapper
ii xserver-xorg-video-ati 1:7.9.0-1
amd64 X.Org X server -- AMD/ATI display
driver wrapper
ii xserver-xorg-video-mach64 6.9.5-1+b2
amd64 X.Org X server -- ATI Mach64 display
driver
ii xserver-xorg-video-r128 6.10.2-1
amd64 X.Org X server -- ATI r128 display
driver
ii xserver-xorg-video-radeon 1:7.9.0-1
amd64 X.Org X server -- AMD/ATI Radeon
display driver
Compiz related:
ii compiz-reloaded 0.8.14-0stretch1 all OpenGL window and compositing manager
ii compiz-reloaded-bcop 0.8.14-0stretch1 all Compiz Reloaded option code
generator
ii compiz-reloaded-core 0.8.14-0stretch1 amd64 OpenGL window and compositing
manager
ii compiz-reloaded-dev 0.8.14-0stretch1 amd64 OpenGL window and compositing
manager - development files
ii compiz-reloaded-gtk 0.8.14-0stretch1 amd64 OpenGL window and compositing
manager - Gtk window decorator
ii compiz-reloaded-mate 0.8.14-0stretch1 amd64 OpenGL window and compositing
manager - MATE window decorator
ii compiz-reloaded-plugins 0.8.14-0stretch1 amd64 OpenGL window and compositing
manager - plugins
ii compiz-reloaded-plugins-experimental 0.8.14-0stretch1 amd64 Compiz Reloaded
plugins - "unsupported" collection
ii compiz-reloaded-plugins-extra 0.8.14-0stretch1 amd64 Compiz Reloaded plugins
- extra collection
ii compiz-reloaded-plugins-main 0.8.14-0stretch1 amd64 Compiz Reloaded plugins
- main collection
ii compizconfig-settings-manager-reloaded 0.8.14-0stretch1 amd64 Compizconfig
Settings Manager
ii emerald 0.8.14-0stretch1 amd64 Decorator for compiz-reloaded
ii libcompizconfig-reloaded-0 0.8.14-0stretch1 amd64 Configuration settings
library for compiz-reloaded
ii libemeraldengine0 0.8.14-0stretch1 amd64 Decoration engines for
compiz-reloaded
ii python-compizconfig-reloaded 0.8.14-0stretch1 amd64 Compizconfig bindings
for python
ii emerald 0.8.14-0stretch1 amd64 Decorator for compiz-reloaded
ii emerald-themes 0.8.14-0stretch1 all Themes for emerald window decorator
ii libemeraldengine0 0.8.14-0stretch1 amd64 Decoration engines for
compiz-reloaded
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=102511
Bug ID: 102511
Summary: RV770 error on change dpm balanced<->battery
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: rob.mackinnon(a)gmail.com
* Overview:
I decided today I would troubleshoot/source an error that has been plaguing my
dmesg:
[drm:btc_dpm_set_power_state [radeon]] *ERROR*
rv770_restrict_performance_levels_before_switch failed
Over all this bug may or may not be related to #91375. I dug into the DPM
setting and levels and was happy to find that switching from "performance" to
"battery" (and vice versa) did not reproduce this bug. What did reproduce the
bug was switching from "balanced" and "battery" (and vice versa).
Kernel version: 4.11.12
Linux Firmware version: 20170519
X.org server version: 1.19.3
Mesa version: 17.2.0_rc5
libdrm version: 2.4.82
Gnome version: 3.24
* Steps to Reproduce:
echo battery > /sys/class/drm/card0/device/power_dpm_state
echo balanced > /sys/class/drm/card0/device/power_dpm_state
* Actual Result:
- DPMS change level changes as expected.
- Dmesg:
[ 3302.814889] [drm:btc_dpm_set_power_state [radeon]] *ERROR*
rv770_restrict_performance_levels_before_switch failed
[ 3316.661933] [drm:btc_dpm_set_power_state [radeon]] *ERROR*
rv770_restrict_performance_levels_before_switch failed
* Expected result:
- DPMS change level changes as expected.
- No error messages in dmesg.
* Additional Info:
Also, not sure if this is related or not, when switching from "battery" to
"performance" there sometimes appears to be an initial clocking issue (which I
believe is related to #93753). Switching back and forth a few times seems to
clean it. Unsure the cause. Another note, upon further inspection of my DPMS
settings, I noticed the drastic differences between "balanced" and "battery"
`sclk`s. My understand (which could be faulty) is that `sclk` drives the
clocking for single displays, while `mclk` for multiple. My laptop rig has 2 DP
displays (3 if I could get it to drive the LVDS display with the 2 DPs, but
that is another issue for another bug another day)
# echo battery > /sys/class/drm/card0/device/power_dpm_state
# cat /sys/kernel/debug/dri/0/radeon_pm_info
uvd vclk: 0 dclk: 0
power level 2 sclk: 30000 mclk: 30000 vddc: 900 vddci: 0
# echo balanced > /sys/class/drm/card0/device/power_dpm_state
# cat /sys/kernel/debug/dri/0/radeon_pm_info
uvd vclk: 0 dclk: 0
power level 0 sclk: 25000 mclk: 90000 vddc: 1100 vddci: 0
# echo performance > /sys/class/drm/card0/device/power_dpm_state
# cat /sys/kernel/debug/dri/0/radeon_pm_info
uvd vclk: 0 dclk: 0
power level 2 sclk: 75000 mclk: 90000 vddc: 1100 vddci: 0
*Video Card:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Seymour [Radeon HD 6400M/7400M Series] (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Radeon HD 6470M
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 37
Region 0: Memory at c0000000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at d4400000 (64-bit, non-prefetchable) [size=128K]
Region 4: I/O ports at 4000 [size=256]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
Kernel modules: radeon
--
You are receiving this mail because:
You are the assignee for the bug.