dri-devel November 2017

dri-devel@lists.freedesktop.org

243 participants
1622 discussions

[Bug 101213] Kernel 4.11: amdgpu regression causes artifacts OLAND amd gpu gcn 1.0
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=101213 Bug ID: 101213 Summary: Kernel 4.11: amdgpu regression causes artifacts OLAND amd gpu gcn 1.0 Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: eutychios23(a)gmail.com The display Manager,part of the desktop and any graphics app i run get severe artifacts on any kernel 4.11.x version with amdgpu enabled, whereas in 4.10.17 all is working good. Reproduce: Install kernel 4.11 and later with SIK=y, blacklist radeon, install xf86-amdgpu, enable the amdgpu module and boot the kernel. Same regression existed in kernels 4.10.2 and lower but was fixed after the 4.10.3 update -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 103403] something going on across the gpu DAC and monitor.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 7

[Bug 102800] DRI_PRIME regression- radeon: Failed to allocate virtual address for buffer
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 21

[Bug 102659] Radeon 7970M Lockup
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 8

[Bug 102599] Window decoration not being painted with DRI3 and Compiz-Reloaded+Emerald
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 5

[Bug 102511] RV770 error on change dpm balanced<->battery
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 6

[Bug 102497] Fatal error during GPU init when using an aarch64 board
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=102497 Bug ID: 102497 Summary: Fatal error during GPU init when using an aarch64 board 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: bero(a)lindev.ch Putting a Radeon graphics card into the PCI slot of an Aarch64 board (the particular one I tried is the Solidrun MACCHIATObin) results in: [Wed Jul 12 14:01:10 2017] [drm] Initialized drm 1.1.0 20060810 [Wed Jul 12 14:01:10 2017] [drm] radeon kernel modesetting enabled. [Wed Jul 12 14:01:10 2017] [drm] initializing kernel modesetting (RV620 0x1002:0x95C5 0x174B:0xE400). [Wed Jul 12 14:01:10 2017] [drm] register mmio base: 0xF6120000 [Wed Jul 12 14:01:10 2017] [drm] register mmio size: 65536 [Wed Jul 12 14:01:10 2017] ATOM BIOS: [Wed Jul 12 14:01:10 2017] [drm] GPU not posted. posting now... [Wed Jul 12 14:01:10 2017] radeon 0000:01:00.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used) [Wed Jul 12 14:01:10 2017] radeon 0000:01:00.0: GTT: 512M 0x0000000020000000 - 0x000000003FFFFFFF [Wed Jul 12 14:01:10 2017] [drm] Detected VRAM RAM=512M, BAR=0M [Wed Jul 12 14:01:10 2017] [drm] RAM width 64bits DDR [Wed Jul 12 14:01:10 2017] [TTM] Zone kernel: Available graphics memory: 1889730 kiB [Wed Jul 12 14:01:10 2017] [TTM] Initializing pool allocator [Wed Jul 12 14:01:10 2017] [TTM] Initializing DMA pool allocator [Wed Jul 12 14:01:10 2017] radeon 0000:01:00.0: Fatal error during GPU init [Wed Jul 12 14:01:10 2017] [drm] radeon: finishing device. [Wed Jul 12 14:01:10 2017] [TTM] Trying to take down uninitialized memory manager type 1 [Wed Jul 12 14:01:10 2017] [TTM] Finalizing pool allocator [Wed Jul 12 14:01:10 2017] [TTM] Finalizing DMA pool allocator [Wed Jul 12 14:01:10 2017] [TTM] Zone kernel: Used memory at exit: 0 kiB [Wed Jul 12 14:01:10 2017] [drm] radeon: ttm finalized [Wed Jul 12 14:01:10 2017] radeon: probe of 0000:01:00.0 failed with error -12 I've tried 3 different radeon cards: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 LE [Radeon HD 3450] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530LE [Radeon X1600/X1650 PRO] All behave the exact same. I presume the problem is caused by the (lack of) BIOS on aarch64 boards not initializing the GPU the same way an x86 box does. This is on kernel 4.4.52 (latest kernel supported by the board; could try pulling DRI patches from newer kernels if there's any hope of changes being there already), libdrm 2.4.82 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 102048] Radeon module takes over two seconds to initialize on a Radeon HD 8470D (Richland)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=102048 Bug ID: 102048 Summary: Radeon module takes over two seconds to initialize on a Radeon HD 8470D (Richland) Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: paulepanter(a)users.sourceforge.net Created attachment 133255 --> https://bugs.freedesktop.org/attachment.cgi?id=133255&action=edit Output of `dmesg` Starting Linux with `initcall_debug` shows that the radeon module takes over two seconds to load on a Asus F2A85-M PRO. ``` initcall radeon_init+0x0/0xaf [radeon] returned 0 after 2278773 usecs ``` ``` $ lspci -s 0:01.0 -nn 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] [1002:9996] ``` Please find the Linux messages captured by running `dmesg` attached. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 101987] Loud fan and maximum GPU fan speed
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=101987 Bug ID: 101987 Summary: Loud fan and maximum GPU fan speed 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: damian.szymanski.ds(a)gmail.com Created attachment 133152 --> https://bugs.freedesktop.org/attachment.cgi?id=133152&action=edit hw-info detalis log Hi. Sorry for all mistake but Im newbie ans sorry for my poor english. I have Radeon HD 5850 and I think something is wrong with him. So even with minimal GPU load, the fan seems to be spinning up to maximum speed, and the fan itself does not mercilessly make a lot of noise but only on open source driver with Mesa. On old legacy fglrx driver all is fine, same as on Windows OS. So I think worth to report this issue. For explain. >From last time I still use AMD Catalyst driver, because I have this issues with open source driver. My Linux distro Mageia 5 still provide fglrx driver, so I still use it but now they release Mageia 6 and old Mageia 5 is supported only for next 3 months. So I need to upgrade or swith distro. Trying few times install on second partitions other Linux distros like Ubuntu 16.04 and 17.04 and Mageia 6 and OpenMandriva LX3 but with this all distro I have still the same issue - noisy gpu fan and almost 100% speed on even low gpu load. So only old Mageia 5 with fglrx or Windows 7 OS can get me silence when I try watch movie, browse internet or playing games. For example, when I start game (e.g free) Dota 2 on Mageia 5 with fglrx, and play it my GPU is silence and the fan is barely audible. But when I boot to other Linux with open source driver with mesa like Ubuntu/Mageia6/OpenMandriva and just start game, even in dota2 main menu I hear the fan spin faster, and faster and faster causing a lot of noise. This is on all games and movies in vlc, smplayer or mpv, even on chromium/chrome or firefox. Trying various mesa version and few version of kernel. Still the same. So if on Linux with fglrx is all fine and if on Windows 7 all is fine and only with Linux with Radeon+Mesa have issue, so it is a bug? Sorry guys, Im newbie and I don't know what I should doing with. Bug? Not a bug? Any solution or fix? Or maybe should I get more info? Help :) -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 101723] hdmi unplug not changing connector status
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=101723 Bug ID: 101723 Summary: hdmi unplug not changing connector status Product: DRI Version: unspecified Hardware: All OS: Linux (All) Status: NEW Severity: minor Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: aki.lemmetyinen(a)gmail.com Created attachment 132558 --> https://bugs.freedesktop.org/attachment.cgi?id=132558&action=edit Small patch to fix the problem I made a quick script for my HP Pavilion dv7 to automatically switch audio to hdmi and back at hotplug event, but I noticed that the driver do not react properly to plug/unplug. /sys/class/drm/card0-HDMI-A-1/status was "connected" even after unplugging the cable. After looking at the code it seemed that in case of cable disconnected there is not point where hotplug state is polled. Function radeon_connector_hotplug do not do much with hdmi and radeon_hotplug_work_func cals drm_helper_hpd_irq_event which calls radeon_dvi_detect where, in case of disconnected cable, it return with connector_status_connected, just throwing an error for missing EDID. It looks like there would maybe be a need for a bigger rewrite of hotplug code, but just to get connector state working properly, I added these few lines to radeon_connectors.c. -- You are receiving this mail because: You are the assignee for the bug.

1 2

← Newer
1
2
3
4
5
6
7
...
163
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel November 2017