dri-devel May 2013

dri-devel@lists.freedesktop.org

116 participants
705 discussions

[Bug 44341] New: Radeon HD6990M: HDMI audio output works now! Kernel gives new warning
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '15

19 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=44341 Summary: Radeon HD6990M: HDMI audio output works now! Kernel gives new warning Product: Drivers Version: 2.5 Kernel Version: 3.5.0-rc6 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: cfroemmel(a)web.de Regression: No Created an attachment (id=75061) --> (https://bugzilla.kernel.org/attachment.cgi?id=75061) kernel's warning It seems that hdmi audio is working now for radeon 69xx series. Thanks for that! It did not on rc3. But there is also a new warning loading the driver that may be interesting. Nevertheless system seems to run good (and with audio!) -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 20

[Bug 44831] New: Radeon HD6970: HDMI audio doesn't work
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '15

19 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=44831 Summary: Radeon HD6970: HDMI audio doesn't work Product: Drivers Version: 2.5 Kernel Version: 3.5.0-rc7 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: valentyn.pavliuchenko(a)gmail.com Regression: No Created an attachment (id=75441) --> (https://bugzilla.kernel.org/attachment.cgi?id=75441) dmesg Radeon Wiki says that HDMI audio should work with 3.5 kernel, however it doesn't. Sound device exists, but there's no actual sound. Video is ok. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 6

[Bug 44851] New: resume to black screen
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '15

19 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=44851 Summary: resume to black screen Product: Drivers Version: 2.5 Kernel Version: 3.5.0-3 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: energonic(a)gmail.com Regression: No System: iMac 11,2 (mid2010) with AMD radeon 4670. kernel 3.5.0-3 used on ubuntu 12.10. No swap partition. Boot requires nomodeset on kernel command line, else black screen (even for text-only boot. Radeon module disconnects wrong display port). Resume after suspend shows black screen, but reboots using Ctl-Alt-Del, so has resumed from suspend. Suspect kms invoked on resume and radeon disconnects wrong display port. Same behaviour on archlinux using kernel 3.4.4-1. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 12

[Bug 29842] New: Radeon runs very hot
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '15

19 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=29842 Summary: Radeon runs very hot Product: Drivers Version: 2.5 Kernel Version: 2.6.38-rc6 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: psusi(a)cfl.rr.com Regression: No The newer kernels read the temperature of my Radeon card, and report that it is running at around 80 C on an idle desktop. For comparison, my CPU is only 34 C. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

6 26

[Bug 64471] New: Radeon HD6570 lockup in Brütal Legend
by bugzilla-daemon＠freedesktop.org 07 Feb '15

07 Feb '15

https://bugs.freedesktop.org/show_bug.cgi?id=64471 Priority: medium Bug ID: 64471 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon HD6570 lockup in Brütal Legend Severity: major Classification: Unclassified OS: Linux (All) Reporter: zboszor(a)pr.hu Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 79165 --> https://bugs.freedesktop.org/attachment.cgi?id=79165&action=edit Lockup from "new game" I tried Brütal Legend on Fedora 18/x86_64, the game itself if i386. The system has these newer-than-Fedora18 components: kernel 3.9+ (commit 51a26ae7a14b85c99c9be470c2d28eeeba0f26a3) libdrm 2.4.44 from 2.4.44-2.fc20 SRPM from Koji recompiled on F18 llvm-3.3 from May 7, before branching to 3.3 was done mesa 9.2 from May 7, commit was around 03ef60681e61a52dee7fa3285618c313cf13f50c compiled into an RPM with float textures enabled: $ rpm -q mesa-libGL mesa-libGL-9.2-0.1.fc18.x86_64 mesa-libGL-9.2-0.1.fc18.i686 The game makes the Radeon chip lock up, reliably at the same point, which is when the game starts after the long cutscene. Attached are two dmesgs, showing the same lockup. The first occurred when I started a new game and watched through the cutscene. The second occurred when I tried to continue the auto-saved game. -- You are receiving this mail because: You are the assignee for the bug.

1 33

[Bug 64867] New: Hangs on Cayman (HD6950) when watching flash/using vdpau
by bugzilla-daemon＠freedesktop.org 27 Jan '15

27 Jan '15

https://bugs.freedesktop.org/show_bug.cgi?id=64867 Priority: medium Bug ID: 64867 Assignee: dri-devel(a)lists.freedesktop.org Summary: Hangs on Cayman (HD6950) when watching flash/using vdpau Severity: normal Classification: Unclassified OS: Linux (All) Reporter: serafean(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 79658 --> https://bugs.freedesktop.org/attachment.cgi?id=79658&action=edit dmesg after X freeze When watching a flash video (opera + flash-11.2.202.262 ) the kernel log starts filling up with [ 7009.603310] radeon 0000:01:00.0: GPU fault detected: 146 0x0e677004 [ 7009.603313] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [ 7009.603316] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 to sometimes eventually hang the GPU. When this starts appearing there is graphic corruption everywhere. I also managed to reproduce this when playing back a video using mplayer with the vdpau backend. ( EnableLinuxHWVideoDecode=1 is commented out in /etc/adobe/mms.cfg) I managed to get a dmesg output after the GPU hang (attached) and then tried to save what is in /sys/kernel/debug/dri/0 but not knowing which was important, tried to do it in a bash for cycle, and got a complete hang. linux-3.10-rc1 mesa, libdrm, radeon ddx from git. might be related to https://bugs.freedesktop.org/show_bug.cgi?id=62959 , but piglit just finished fine. (fine = didn't hang in this case, still a bunch of "radeon_gem_object_create:69 alloc size 1365Mb bigger than 256Mb limit" in the logs). Additional info : I have a dual screen setup. Anything more you need, I'll be happy to provide. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 56519] New: [r300g, bisected] piglit max-texture-size fails
by bugzilla-daemon＠freedesktop.org 20 Jan '15

20 Jan '15

https://bugs.freedesktop.org/show_bug.cgi?id=56519 Priority: medium Bug ID: 56519 Keywords: regression CC: brianp(a)vmware.com Assignee: dri-devel(a)lists.freedesktop.org Summary: [r300g, bisected] piglit max-texture-size fails Severity: normal Classification: Unclassified OS: All Reporter: pavel.ondracka(a)email.cz Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa Created attachment 69224 --> https://bugs.freedesktop.org/attachment.cgi?id=69224&action=edit dmesg There were some errors even before this commit but the test passed. There sre also some error messages in dmesg (attached). Regression caused by e6eaa85a43616ba6f431276ab94a3b19dd524986 Author: Brian Paul <brianp(a)vmware.com> Date: Sat Sep 15 10:30:20 2012 -0600 mesa: rework texture size error checking ./bin/max-texture-size -auto r300: DRM version: 2.24.0, Name: ATI RV530, ID: 0x71c5, GB: 1, Z: 2 r300: GART size: 509 MB, VRAM size: 256 MB r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: YES GL_PROXY_TEXTURE_1D, Internal Format = GL_RGBA8, Largest Texture Size = 4096 GL_PROXY_TEXTURE_1D, Internal Format = GL_RGBA16, Largest Texture Size = 4096 GL_PROXY_TEXTURE_1D, Internal Format = GL_RGBA32F, Largest Texture Size = 4096 GL_PROXY_TEXTURE_2D, Internal Format = GL_RGBA8, Largest Texture Size = 4096 GL_PROXY_TEXTURE_2D, Internal Format = GL_RGBA16, Largest Texture Size = 4096 GL_PROXY_TEXTURE_2D, Internal Format = GL_RGBA32F, Largest Texture Size = 4096 GL_PROXY_TEXTURE_RECTANGLE, Internal Format = GL_RGBA8, Largest Texture Size = 4096 GL_PROXY_TEXTURE_RECTANGLE, Internal Format = GL_RGBA16, Largest Texture Size = 4096 GL_PROXY_TEXTURE_RECTANGLE, Internal Format = GL_RGBA32F, Largest Texture Size = 4096 GL_PROXY_TEXTURE_CUBE_MAP, Internal Format = GL_RGBA8, Largest Texture Size = 4096 GL_PROXY_TEXTURE_CUBE_MAP, Internal Format = GL_RGBA16, Largest Texture Size = 4096 GL_PROXY_TEXTURE_CUBE_MAP, Internal Format = GL_RGBA32F, Largest Texture Size = 3347 GL_PROXY_TEXTURE_3D, Internal Format = GL_RGBA8, Largest Texture Size = 645 GL_PROXY_TEXTURE_3D, Internal Format = GL_RGBA16, Largest Texture Size = 512 GL_PROXY_TEXTURE_3D, Internal Format = GL_RGBA32F, Largest Texture Size = 406 GL_TEXTURE_1D, Internal Format = GL_RGBA8, Largest Texture Size = 4096 GL_TEXTURE_1D, Internal Format = GL_RGBA16, Largest Texture Size = 4096 GL_TEXTURE_1D, Internal Format = GL_RGBA32F, Largest Texture Size = 4096 GL_TEXTURE_2D, Internal Format = GL_RGBA8, Largest Texture Size = 4096 GL_TEXTURE_2D, Internal Format = GL_RGBA16, Largest Texture Size = 4096 GL_TEXTURE_2D, Internal Format = GL_RGBA32F, Largest Texture Size = 4096 r300: CS space validation failed. (not enough memory?) Skipping rendering. GL_TEXTURE_RECTANGLE, Internal Format = GL_RGBA8, Largest Texture Size = 4096 GL_TEXTURE_RECTANGLE, Internal Format = GL_RGBA16, Largest Texture Size = 4096 GL_TEXTURE_RECTANGLE, Internal Format = GL_RGBA32F, Largest Texture Size = 4096 GL_TEXTURE_CUBE_MAP, Internal Format = GL_RGBA8, Largest Texture Size = 4096 r300: CS space validation failed. (not enough memory?) Skipping rendering. r300: CS space validation failed. (not enough memory?) Skipping rendering. r300: CS space validation failed. (not enough memory?) Skipping rendering. r300: CS space validation failed. (not enough memory?) Skipping rendering. r300: CS space validation failed. (not enough memory?) Skipping rendering. r300: CS space validation failed. (not enough memory?) Skipping rendering. GL_TEXTURE_CUBE_MAP, Internal Format = GL_RGBA16, Largest Texture Size = 4096 radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 radeon: Failed to allocate a buffer: radeon: size : 805306368 bytes radeon: alignment : 2048 bytes radeon: domains : 6 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D Mesa: User error: GL_OUT_OF_MEMORY in glTexSubImage GL_TEXTURE_CUBE_MAP, Internal Format = GL_RGBA32F, Largest Texture Size = 4096 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D(image too large) Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D(image too large) Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D(image too large) Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D(image too large) Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D(image too large) Mesa: User error: GL_OUT_OF_MEMORY in glTexImage2D(image too large) Mesa: User error: GL_OUT_OF_MEMORY in glTexSubImage GL_TEXTURE_3D, Internal Format = GL_RGBA8, Largest Texture Size = 4096 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage3D(image too large) Mesa: User error: GL_INVALID_OPERATION in glTexSubImage3D(invalid texture image) Unexpected GL error: 0x502 GL_TEXTURE_3D, Internal Format = GL_RGBA16, Largest Texture Size = 4096 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage3D(image too large) Mesa: User error: GL_INVALID_OPERATION in glTexSubImage3D(invalid texture image) Unexpected GL error: 0x502 GL_TEXTURE_3D, Internal Format = GL_RGBA32F, Largest Texture Size = 4096 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage3D(image too large) Mesa: User error: GL_INVALID_OPERATION in glTexSubImage3D(invalid texture image) Unexpected GL error: 0x502 PIGLIT: {'result': 'fail' } GPU:RV530 Kernel: 3.6.2-4.fc17.i686 mesa: 96ed6c90eff58ce030c39c2b4db6daf512586b34 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 34969] New: [nouveau] Card lockup on openarena
by bugzilla-daemon＠freedesktop.org 09 Dec '14

09 Dec '14

https://bugs.freedesktop.org/show_bug.cgi?id=34969 Summary: [nouveau] Card lockup on openarena Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/other AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: mad.f3ka(a)gmail.com Created an attachment (id=44068) --> (https://bugs.freedesktop.org/attachment.cgi?id=44068) messages.log part Each time I try to start openarena or any other game, card locks up (not in menu, but in game). I'm not sure, but log in messages seems to be related to this issue (see messages attachment). Software versions: kernel 2.6.37.2 libdrm 2.4.23 mesa 7.10.1 xf86-video-nouveau 0.0.16_git20101217 Hardware: 06:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 22

[Bug 63192] New: [nouveau] drmModeSetCursor->nouveau_bo_rd32->ioread32 provides high cpu load when using weston drm-compositor
by bugzilla-daemon＠freedesktop.org 09 Dec '14

09 Dec '14

https://bugs.freedesktop.org/show_bug.cgi?id=63192 Priority: medium Bug ID: 63192 Assignee: dri-devel(a)lists.freedesktop.org Summary: [nouveau] drmModeSetCursor->nouveau_bo_rd32->ioread32 provides high cpu load when using weston drm-compositor Severity: normal Classification: Unclassified OS: Linux (All) Reporter: vova7890(a)mail.ru Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/other Product: DRI Weston runned in drm-mode provide very high cpu load on mouse moving. I don`t think that the bug of weston, seems problem in nouveau drm. At launch weston have a log: ... [24465.734894] nouveau W[ PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004 [24465.748153] nouveau W[ PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004 [24521.950788] nouveau W[ PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004 [24521.955032] nouveau W[ PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004 ... ioread32_native(ioread32 on litle-endian) using 100% of cpu core. If in weston comment out drmModeSetCursor - cpu load is normal, but no see cursor ofcourse. They copying cursor(64x64) from bo-object. Seems TTM iomem access provide very high cpu load... On radeon it works smoothly and no have very high cpu load. Kernel 3.9-rc5 (x86_64) Wayland/Weston: git Mesa: git libdrm: git -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 57352] New: [nouveau] Kernel Tux logo incorrectly displayed at boot
by bugzilla-daemon＠freedesktop.org 09 Dec '14

09 Dec '14

https://bugs.freedesktop.org/show_bug.cgi?id=57352 Priority: medium Bug ID: 57352 Assignee: dri-devel(a)lists.freedesktop.org Summary: [nouveau] Kernel Tux logo incorrectly displayed at boot Severity: normal Classification: Unclassified OS: All Reporter: bonbons67(a)internet.lu Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/other Product: DRI When booting with build-in nouveau (KMS enabled) the Tux logos displayed are not recognizable. It looks like incorrect tiling configuration of either source or destination buffer when rendering the logo. Normal fbcon console text displays as expected. This happens with linux-3.7-rc5 and newer (don't know since when). Hardware is MacBookAir with GeForce 9400M (C79) [10de:0870]. (screenshot following later on) -- You are receiving this mail because: You are the assignee for the bug.

1 2

← Newer
1
...
26
27
28
29
30
31
32
...
71
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel May 2013