dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 86351] New: HDMI audio garbled output on Radeon R9 280X
by bugzilla-daemon＠bugzilla.kernel.org 23 Mar '19

23 Mar '19

https://bugzilla.kernel.org/show_bug.cgi?id=86351 Bug ID: 86351 Summary: HDMI audio garbled output on Radeon R9 280X Product: Drivers Version: 2.5 Kernel Version: 3.17 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: joker(a)netswarm.net Regression: No Created attachment 153891 --> https://bugzilla.kernel.org/attachment.cgi?id=153891&action=edit dmesg output Any sound played back over HDMI results in garbled audio output. When playing audio at 24000hz or below (19200Hz also tested) playback starts to work normaly without the constant choppyness. What also works is 44100Hz in Mono. It behaves like a data bandwith issue that kicks in above 24000hz Stereo or 44100Hz Mono. All test are done directly talking to the alsa device. This means no pulseaudio or dmix or similar processing. "plughw" had to be used because the hardware does not allow low rates like 24000. During all Test a perfectly fine and stable 1080p image is displayed over HDMI. (No dropouts at all). This hardware setup has also be successfully tested using Windows. (Incl. Multi channel PCM 6.0 for lot's of audio bandwidth) Working Audio Tests: -------------------- speaker-test -r 24000 -c2 speaker-test -r 24000 -c6 (multi channel PCM works too) mpg123 -r 24000 <file> mpg123 -m -r 44100 <file> The peer format detection is pcm 2.0 44100 or 48000 here. It appears the format link doesn't matter, only the actual data bandwidth that's being used) Garbled Audio Tests: -------------------- speaker-test -r 48000 -c2 speaker-test -r 48000 -c6 mpg123 -r 44100 <file> All passthru formats (dts, dolby d, pcm multi channel) get detected my the destination, but after a short period it loses the link and tries to resync. What previously also worked is a HD5570 in the same system which i no longer have access to though. Not sure about the kernel used back then. -- You are receiving this mail because: You are watching the assignee of the bug.

1 35

[Bug 88501] New: AMD/ATI RS690M Console blanks to white
by bugzilla-daemon＠bugzilla.kernel.org 05 Mar '19

05 Mar '19

https://bugzilla.kernel.org/show_bug.cgi?id=88501 Bug ID: 88501 Summary: AMD/ATI RS690M Console blanks to white Product: Drivers Version: 2.5 Kernel Version: 3.6.0-rc5 to 3.18.0-rc4 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: business.kid(a)gmail.com Regression: Yes Created attachment 158181 --> https://bugzilla.kernel.org/attachment.cgi?id=158181&action=edit Git Bisect log, & git visualise o/p Without X running, linux consoles blank after a period adjustable by setterm. Mine does not. It goes white. If I invert the screen colours, it goes whiter. Backlight? I cloned the Linus-stable git and tried it. 3.18.0-rc4 twists this slightly - The FIRST time the screen blanks, it does so correctly; every other time, it blanks to white. I'm a hardware guy, not a software expert. Git bisect gives the output below. Details of the box also attached The box is a HP 6715S, twin core Turion, 3G ram. It's running Slackware-current as of Sept 30th, 2014. LSPCI output attached. Bios Version: ATI 02/13/08,1. -- You are receiving this mail because: You are watching the assignee of the bug.

1 11

[Bug 60623] New: White Screen on boot with radeon.dpm=1
by bugzilla-daemon＠bugzilla.kernel.org 05 Mar '19

05 Mar '19

https://bugzilla.kernel.org/show_bug.cgi?id=60623 Bug ID: 60623 Summary: White Screen on boot with radeon.dpm=1 Product: Drivers Version: 2.5 Kernel Version: 3.11.0-999-generic Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: electrobs(a)gmail.com Regression: No Using the latest ubuntu built kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/, and enabling the boot option of radeon.dpm=1 . Results in a black screen after grub that eventually turns white gradually. Removing the option allows the laptop to function perfectly with the AMD 3650 video card. Hardware: -Lenovo T500 with AMD 3650 and a Intel 4500MHD switchable graphics off. -more info at http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-71785 Software: -clean install of Kubuntu 13.04 with beta ppa enabled for KDE 4.11 rc2 -xorg-edgers ppa enabled -- You are receiving this mail because: You are watching the assignee of the bug.

1 2

[Bug 91110] Textures missing iff character in specific areas in dolphin running Xenoblades Chronicles
by bugzilla-daemon＠freedesktop.org 17 Feb '19

17 Feb '19

https://bugs.freedesktop.org/show_bug.cgi?id=91110 Bug ID: 91110 Summary: Textures missing iff character in specific areas in dolphin running Xenoblades Chronicles Product: Mesa Version: git Hardware: x86-64 (AMD64) URL: https://code.google.com/p/dolphin-emu/issues/detail?id =8688 OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: christian(a)madez.de QA Contact: dri-devel(a)lists.freedesktop.org Iff a character is in specific areas some textures on him are not rendered. In the entry of colony 9 is such an area. The textures are rendered properly on the Intel GPU. There are screenshots, a fifolog and an apitrace at the end of the linked bugreport. The problem appears in Debian Jessie, Sid and mesa-git the last time checked, which was 9 days ago. I compiled mesa-git with CFLAGS = -g -O2 -Wall -std=c99 -Werror=implicit-function-declaration -Werror=missing-prototypes -fno-strict-aliasing -fno-builtin-memcmp -DDEBUG and set $ export LIBGL_DEBUG=verbose $ export MESA_DEBUG=1 $ export EGL_LOG_LEVEL=debug before running dolphin. Running dolphin with the game until the issue appears gives the following output $ dolphin-emu Gtk-Message: Failed to load module "canberra-gtk-module" libGL: screen 0 does not appear to be DRI3 capable libGL: pci id for fd 22: 1002:679a, driver radeonsi libGL: OpenDriver: trying lib/tls/radeonsi_dri.so libGL: OpenDriver: trying lib/radeonsi_dri.so libGL: Can't open configuration file /home/user/.drirc: Arquivo ou diretório não encontrado. libGL: Can't open configuration file /home/user/.drirc: Arquivo ou diretório não encontrado. libGL: Using DRI2 for screen 0 I'm sorry, I don't know how to write a simple GLUT-based test program. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 93747] Proprietary game Minecraft fails to enter fullscreen
by bugzilla-daemon＠freedesktop.org 17 Feb '19

17 Feb '19

https://bugs.freedesktop.org/show_bug.cgi?id=93747 Bug ID: 93747 Summary: Proprietary game Minecraft fails to enter fullscreen Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: andre35822(a)yahoo.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 121095 --> https://bugs.freedesktop.org/attachment.cgi?id=121095&action=edit dmesg output when opening the game and trying to set it in fullscreen I am on Arch Linux with Mesa 11.1, Kernel 4.3.3, llvm 3.7.1-1 and have an AMD 7950. The issue that is occurring is that Minecraft is failing to enter fullscreen with multiple DEs (Openbox, XFCE, and Cinnamon are the ones that I have tried, and all do not properly enter fullscreen). When I hit the fullscreen option in the game, the window sort of turns completely transparent or sometimes the theme of my desktop environment but I can not see anything. I can hear sounds from the game and clicking/pressing keyboard buttons are actually working in the game so it is as if the game is working fine just it is not rendering the window correctly. (I can hear myself breaking blocks). If I quit the game in this state and re-open it, the game will launch in fullscreen, but if I alt-tab or set it back to window mode and try to enter fullscreen mode, the same that I stated above occurs. I would like to note that I am using OpenJRE and not Sun Java's though someone with an AMD GPU and Sun java stated they experience the same issue. So I really think it is down to a mesa bug or something? I am not sure how it works. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 101928] GRID via Wine crashes mid-race
by bugzilla-daemon＠freedesktop.org 17 Feb '19

17 Feb '19

https://bugs.freedesktop.org/show_bug.cgi?id=101928 Bug ID: 101928 Summary: GRID via Wine crashes mid-race Product: Mesa Version: 17.1 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: aaalmosss(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org I get one or more "radeon: mmap failed, errno: 12" on the console, and shortly after the game crashes. This happens after a few minutes of playing, a 3-lap race cannot be finished (I tried multiple locations). The backtrace is probably useless: =>0 0x00bfd5ee in grid (+0x7fd5ee) (0x0544e71c) 1 0x00bfd694 in grid (+0x7fd693) (0x0544e74c) 2 0x0073a732 in grid (+0x33a731) (0x0544e970) 3 0x00884206 in grid (+0x484205) (0x0544e9c4) 4 0x0087260a in grid (+0x472609) (0x0040ef50) 5 0x660f57e8 (0x08244c8b) 0x00bfd5ee: movq %mm0,0x0(%edi) This is the first GRID that is no longer in the Steam store (appid 12750). -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 100979] Radeon r4 on a6-6310(BEEMA) APU hard lockup on hibernate and on second resume from suspend
by bugzilla-daemon＠freedesktop.org 16 Feb '19

16 Feb '19

https://bugs.freedesktop.org/show_bug.cgi?id=100979 Bug ID: 100979 Summary: Radeon r4 on a6-6310(BEEMA) APU hard lockup on hibernate and on second resume from suspend Product: DRI Version: DRI 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: soprwa(a)gmail.com I'm using kernel 4.11 on gentoo with SI/CIK enabled on Lenovo G50-45 Notebook. Machine has AMD APU A6 6130 with Radeon r4 graphics card (Beema/Mullins). This CPU supports olny AMD IOMMU v1. There is no discrete graphic card on it, APU only. When I try to hibernate this notebook it doesn't turning off. I have to press power button to reboot the machine. Similar situation is on "radeon" driver, and I had submitted bug report about this on kernel's bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=191571 But in this situation I'm unable to bisect because as I remember correctly problem always occur on amdgpu driver, so I think those two can correlate with each other. (dmesg form hibernation process attached). As for suspend. I can suspend/resume machine successfully only once in a row. Second time machine suspends correctly, but on resume I have hard lockup, fans are spinning on full rpm's and I cannot do anything but pressing power button to reboot(cold boot) the netbook. Moreover in dmesg after first suspend I've got error messages: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed Attachments: 1. Log after clean start. 2. Kernel's config file. 3. Log after hibernation process. 4. Log after first suspend/resume. 5. Log after second suspend/resume. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 99923] HITMAN (2016) having lighting and artefacting, and overly light room.
by bugzilla-daemon＠freedesktop.org 27 Jan '19

27 Jan '19

https://bugs.freedesktop.org/show_bug.cgi?id=99923 Bug ID: 99923 Summary: HITMAN (2016) having lighting and artefacting, and overly light room. 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: thedribbleondo(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 129874 --> https://bugs.freedesktop.org/attachment.cgi?id=129874&action=edit All the screenshots shown on imgur in case imgur goes down or something. When Running Mesa 17.1 git, upon entering any level, the game will start having black splotches and lighting missing/ not rendered correctly. This can be seen in this album here: http://imgur.com/a/k54kc This appears to be a problem with git only, as mesa 13.0.4 isn't affected by this bug... -- You are receiving this mail because: You are the assignee for the bug.

1 48

[Bug 190971] New: amdgpu (on Kabini) fails to resume, atombios stuck executing BA98
by bugzilla-daemon＠bugzilla.kernel.org 25 Jan '19

25 Jan '19

https://bugzilla.kernel.org/show_bug.cgi?id=190971 Bug ID: 190971 Summary: amdgpu (on Kabini) fails to resume, atombios stuck executing BA98 Product: Drivers Version: 2.5 Kernel Version: 4.9 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: blade(a)debian.org Regression: No Created attachment 248421 --> https://bugzilla.kernel.org/attachment.cgi?id=248421&action=edit Kernel messages Hardware: Lenovo Thinkpad Edge E145 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Root Complex 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] This system works fine with the Radeon driver. With amdgpu and CONFIG_DRM_AMDGPU_CIK=y , it works until the next suspend-to-ram cycle. Then the system comes up but the screen remains dark. See attachment for kernel logs. The same thing happened earlier when I tested AMDGPU with 4.8.x kernels. -- You are receiving this mail because: You are watching the assignee of the bug.

1 2

[Bug 97639] Intermittent flickering artifacts with AMD R7 260x
by bugzilla-daemon＠freedesktop.org 14 Jan '19

14 Jan '19

https://bugs.freedesktop.org/show_bug.cgi?id=97639 Bug ID: 97639 Summary: Intermittent flickering artifacts with AMD R7 260x Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: nucrap(a)hotmail.com Created attachment 126306 --> https://bugs.freedesktop.org/attachment.cgi?id=126306&action=edit my Xorg.0.log Hi, I am using an MSI R7 260x OC with the new amdgpu driver. Everything seems to run fine (I have yet to experience any crashes), however there constantly flicker some artifacts on my screen. In the Xorg.0.log I have noticed many suspicious error messages similar to this: AMDGPU(0): amdgpu_dri2_flip_event_handler: Pageflip completion event has impossible msc 100169 < target_msc 100170 Looking at the description in the source code, it fits the bug I experience: > Check for too small vblank count of pageflip completion, taking wraparound > into account. This usually means some defective kms pageflip completion, > causing wrong (msc, ust) return values and possible visual corruption. I saw there was a similar bug (bug#91540), but it has been marked as fixed some time ago. My config: Linux v4.7.2 (amdgpu, cik and powerplay enabled) xf86-video-ati v7.7.0 mesa v12.0.1 xorg-drivers v1.17 xserver v1.17.4 KDE Plasma 5 (kwin) If you need any further info please ask. -- You are receiving this mail because: You are the assignee for the bug.

1 15

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2017