dri-devel September 2014

dri-devel@lists.freedesktop.org

173 participants
1045 discussions

[Bug 78951] New: gl_PrimitiveID is zero if no geometry shader is present
by bugzilla-daemon＠freedesktop.org 29 Jan '15

29 Jan '15

https://bugs.freedesktop.org/show_bug.cgi?id=78951 Priority: medium Bug ID: 78951 Assignee: dri-devel(a)lists.freedesktop.org Summary: gl_PrimitiveID is zero if no geometry shader is present Severity: normal Classification: Unclassified OS: All Reporter: pavol(a)klacansky.com Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/r600 Product: Mesa I case there is no geometry shader attached to program, gl_PrimitiveID is always zero. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[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 77002] New: problems with kernel 3.14
by bugzilla-daemon＠freedesktop.org 22 Jan '15

22 Jan '15

https://bugs.freedesktop.org/show_bug.cgi?id=77002 Priority: medium Bug ID: 77002 Assignee: dri-devel(a)lists.freedesktop.org Summary: problems with kernel 3.14 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: bgunteriv(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 96846 --> https://bugs.freedesktop.org/attachment.cgi?id=96846&action=edit dmesg not sure where this bug belongs. having great issues with the new kernel 3.14 on my system trying to play any type of media -- video or music. currently running kernel 3.13 version 8. is the most stable. here are my logs when running kernel 3.14 dmesg | pastebinit http://paste.ubuntu.com/7033651/ cat ~/.xbmc/temp/xbmc.log | pastebinit http://paste.ubuntu.com/7033687/ cat /var/log/Xorg.0.log | pastebinit http://paste.ubuntu.com/7033653/ DISPLAY=:0 vdpauinfo | pastebinit http://paste.ubuntu.com/7033656/ dpkg -l |grep mesa | pastebinit http://paste.ubuntu.com/7033657/ and here's a log file when trying to play a video... both online, and from my hard drive. and a music file (which made XBMC freeze): http://paste.ubuntu.com/7033704/ and yes. i get the same results when running the most recent "stable" version of the kernel 3.14. but can try to get some logs if necessary. -- You are receiving this mail because: You are the assignee for the bug.

1 40

[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 83510] New: Graphical glitches in Unreal Engine 4
by bugzilla-daemon＠freedesktop.org 16 Jan '15

16 Jan '15

https://bugs.freedesktop.org/show_bug.cgi?id=83510 Priority: medium Bug ID: 83510 Assignee: dri-devel(a)lists.freedesktop.org Summary: Graphical glitches in Unreal Engine 4 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: geecko.dev(a)free.fr Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa While all the Linux demos are now running fine, there is some rendering errors left. - Some objects are blurred. It looks like motion blur on objects that don't need it, like cameras, characters or weapons. You can see it in the Elemental Demo or Shooter Game demo. - Some pixels turn black when the camera is static, very noticeable on the sky box in the Mobile Game demo. - It seems that the lighting is too dark in some scenes, can be seen in the Realistic Rendering demo or the Shooter Game demo with the Sanctuary map. HD 7950, mesa-git and llvm-svn on latest Arch Linux. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 80584] New: XCOM: Eenemy Unknown incorrect hair rendering
by bugzilla-daemon＠freedesktop.org 08 Jan '15

08 Jan '15

https://bugs.freedesktop.org/show_bug.cgi?id=80584 Priority: medium Bug ID: 80584 Assignee: dri-devel(a)lists.freedesktop.org Summary: XCOM: Eenemy Unknown incorrect hair rendering Severity: normal Classification: Unclassified OS: Linux (All) Reporter: theamazingjanet(a)googlemail.com Hardware: x86-64 (AMD64) Status: NEW Version: 10.1 Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 101846 --> https://bugs.freedesktop.org/attachment.cgi?id=101846&action=edit XCOM: Enemy Unknown Screenshot 1 Hair on certain characters in XCOM: Enemy Unknown does not look correct. See the attached screenshots. This occurs on both Mesa 10.1.3 + LLVM 3.4 and Mesa git + LLVM 3.4.2 via Oibaf PPA, Ubuntu 14.04. -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 65761] New: HD 7970M Hybrid - hangs and errors and rmmod causes crash
by bugzilla-daemon＠bugzilla.kernel.org 04 Jan '15

04 Jan '15

https://bugzilla.kernel.org/show_bug.cgi?id=65761 Bug ID: 65761 Summary: HD 7970M Hybrid - hangs and errors and rmmod causes crash Product: Drivers Version: 2.5 Kernel Version: 3.13-rc1 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: haagch.christoph(a)googlemail.com Regression: No Created attachment 115961 --> https://bugzilla.kernel.org/attachment.cgi?id=115961&action=edit dmesg with multiple issues 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wimbledon XT [Radeon HD 7970M] muxless, so there's no display outputs on the radeon gpu. With 3.13 and dpm and runtime power management enabled by default this should be getting usable. I did not start X this time. (when starting X on the intel gpu quickly after booting (presumably before radeon is initialized) the display output hangs, which is yet another problem). Dmesg seems to contain several issues. 1. While booting it already produces these before even "dpm initialized" is logged: [ 20.120137] WARNING: CPU: 0 PID: 53 at drivers/gpu/drm/drm_mm.c:578 drm_mm_takedown+0x2e/0x30 [drm]() [ 20.120138] Memory manager not clean during takedown. 2. These are just periodically displayed in the tty: [ 79.179928] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [ 79.181378] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [ 79.182790] [drm:radeon_resume_kms] *ERROR* ib ring test failed (-35). 3. After some time in a tty, I did "rmmod radeon" and got some other issues ending with [ 192.663059] Fixing recursive fault but reboot is needed! and then, after a little while a lot of other errors happen, but they are not captured here in the dmesg. -- You are receiving this mail because: You are watching the assignee of the bug.

1 57

[REGRESSION] i915: failure to see Dell 30" monitor connected to a Lenovo Haswell docking station
by Theodore Ts'o 15 Dec '14

15 Dec '14

I recently upgraded to v3.17-rc3, and on my Lenovo T540p, I can no longer see the my Dell 30" monitor when it is connected via the docking station using a Displayport connector. This worked using 3.16 kernel. If I connect to the monitor using the mini-display, by passing the docking station, things work fine (but of course it's annoying not to be able to use the docking station). Is this a known problem? This is not the first time that we've had regressions with this docking station. It's vaguely reminsicent of https://bugs.freedesktop.org/show_bug.cgi?id=71267 Except the system isn't hanging; it's just not seeing the monitor at all. Thanks, - Ted

2 9

[Bug 82201] New: [HAWAII] GPU doesn't reclock, poor 3D performance
by bugzilla-daemon＠freedesktop.org 12 Dec '14

12 Dec '14

https://bugs.freedesktop.org/show_bug.cgi?id=82201 Priority: medium Bug ID: 82201 Assignee: dri-devel(a)lists.freedesktop.org Summary: [HAWAII] GPU doesn't reclock, poor 3D performance Severity: normal Classification: Unclassified OS: Linux (All) Reporter: kai(a)dev.carbon-project.org Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa No matter what program I run, the clock of the GPU stays: # cat /sys/kernel/debug/dri/*/radeon_pm_info power level avg sclk: 30000 mclk: 15000 power level avg sclk: 30000 mclk: 15000 The attached screenshot shows Portal 2 with a GALLIUM_HUD=fps overlay. The ~30 FPS are in the menu, the 8-15 FPS are in the level. My stack is (base: Debian Testing): GPU: Hawaii PRO [Radeon R9 290] (ChipID = 0x67b1) Linux: Git:~agdf5/linux:drm-next-3.17-rebased-on-fixes:fa78380797 (calls itself 3.16-rc6) Firmware: <http://people.freedesktop.org/~agd5f/radeon_ucode/ucode.tar.gz> > 9e05820da42549ce9c89d147cf1f8e19 /lib/firmware/updates/3.16.0-rc6-citadel/radeon/hawaii_ce.bin > c8bab593090fc54f239c8d7596c8d846 /lib/firmware/updates/3.16.0-rc6-citadel/radeon/hawaii_mc.bin > 3618dbb955d8a84970e262bb2e6d2a16 /lib/firmware/updates/3.16.0-rc6-citadel/radeon/hawaii_me.bin > c000b0fc9ff6582145f66504b0ec9597 /lib/firmware/updates/3.16.0-rc6-citadel/radeon/hawaii_mec.bin > 0643ad24b3beff2214cce533e094c1b7 /lib/firmware/updates/3.16.0-rc6-citadel/radeon/hawaii_pfp.bin > ba6054b7d78184a74602fd81607e1386 /lib/firmware/updates/3.16.0-rc6-citadel/radeon/hawaii_rlc.bin > 11288f635737331b69de9ee82fe04898 /lib/firmware/updates/3.16.0-rc6-citadel/radeon/hawaii_sdma.bin > 284429675a5560e0fad42aa982965fc2 /lib/firmware/updates/3.16.0-rc6-citadel/radeon/hawaii_smc.bin libdrm: Git:master/libdrm-2.4.56 LLVM: SVN:trunk/r214546 (3.6 snapshot) libclc: Git:master/5b48f170c8 Mesa: Git:master/e41cc45361 DDX: Git:master/fbf575cb01 + Patch from http://lists.x.org/archives/xorg-driver-ati/2014-August/026534.html X: 2:1.16.0-1 (1.16.0) Let me know, if you need further information (current Xorg.0.log (attachment 103995), dmesg (attachment 103996) and glxinfo (attachment 103997) can be found attached to bug 82055). -- You are receiving this mail because: You are the assignee for the bug.

1 53

[Bug 79696] New: 10.2.0rc5 GPU stall & Xorg crash while using Geeqie
by bugzilla-daemon＠freedesktop.org 11 Dec '14

11 Dec '14

https://bugs.freedesktop.org/show_bug.cgi?id=79696 Priority: medium Bug ID: 79696 Assignee: dri-devel(a)lists.freedesktop.org Summary: 10.2.0rc5 GPU stall & Xorg crash while using Geeqie Severity: normal Classification: Unclassified OS: All Reporter: marti(a)juffo.org Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 100481 --> https://bugs.freedesktop.org/attachment.cgi?id=100481&action=edit gdm-Xorg:0.log I'm using Arch Linux testing repositories with Mesa 10.2.0rc5 After a rather long session of browsing pictures using the Geeqie image viewer, the display froze up, and after some time passed, Xorg crashed and restarted. The new Xorg had GPU acceleration disabled. I had done a suspend & resume cycle after the last boot, prior to the crash. Versions: ati-dri 10.2.0rc5 mesa 10.2.0rc5 xorg-server 1.15.1 kernel 3.14.4 xf86-video-ati 7.3.0 In the log files: 20:10:27 - resume from suspend 20:58:37 - kernel: 0000:01:00.0: GPU lockup CP stall for more than 10000msec 20:59:04 - Xorg: The kernel rejected CS, see dmesg for more information. 20:59:04 - Xorg segfault 20:59:05 - new Xorg: RADEON(0): Direct rendering disabled Xorg backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x48) [0x584b08] 1: /usr/bin/Xorg (0x400000+0x1887f9) [0x5887f9] 2: /usr/lib/libpthread.so.0 (0x7fb78e9a4000+0xf4b0) [0x7fb78e9b34b0] 3: /usr/lib/xorg/modules/dri/radeonsi_dri.so (0x7fb786e9e000+0x68b7c) [0x7fb786f06b7c] 4: /usr/lib/xorg/modules/dri/radeonsi_dri.so (0x7fb786e9e000+0x6b401) [0x7fb786f09401] 5: /usr/lib/xorg/modules/dri/radeonsi_dri.so (0x7fb786e9e000+0x48884) [0x7fb786ee6884] 6: /usr/lib/xorg/modules/dri/radeonsi_dri.so (0x7fb786e9e000+0x19ac9b) [0x7fb787038c9b] 7: /usr/lib/xorg/modules/dri/radeonsi_dri.so (0x7fb786e9e000+0x1a2dc8) [0x7fb787040dc8] 8: /usr/lib/xorg/modules/dri/radeonsi_dri.so (0x7fb786e9e000+0x1a530c) [0x7fb78704330c] 9: /usr/lib/xorg/modules/dri/radeonsi_dri.so (0x7fb786e9e000+0x13b8e4) [0x7fb786fd98e4] 10: /usr/lib/xorg/modules/dri/radeonsi_dri.so (0x7fb786e9e000+0x13cc50) [0x7fb786fdac50] 11: /usr/lib/libglamor.so.0 (0x7fb78b26d000+0x1e2a7) [0x7fb78b28b2a7] 12: /usr/lib/libglamor.so.0 (0x7fb78b26d000+0x1e892) [0x7fb78b28b892] 13: /usr/lib/libglamor.so.0 (0x7fb78b26d000+0x1f184) [0x7fb78b28c184] 14: /usr/lib/libglamor.so.0 (0x7fb78b26d000+0x1fc70) [0x7fb78b28cc70] 15: /usr/lib/libglamor.so.0 (0x7fb78b26d000+0x524c) [0x7fb78b27224c] 16: /usr/lib/libglamor.so.0 (0x7fb78b26d000+0x5b74) [0x7fb78b272b74] 17: /usr/lib/libglamor.so.0 (0x7fb78b26d000+0x6bb5) [0x7fb78b273bb5] 18: /usr/lib/libglamor.so.0 (0x7fb78b26d000+0x6e9a) [0x7fb78b273e9a] 19: /usr/bin/Xorg (miCopyRegion+0x1ad) [0x564f7d] 20: /usr/bin/Xorg (miDoCopy+0x456) [0x565506] 21: /usr/lib/libglamor.so.0 (0x7fb78b26d000+0x6edd) [0x7fb78b273edd] 22: /usr/bin/Xorg (0x400000+0x112258) [0x512258] 23: /usr/bin/Xorg (0x400000+0xced0a) [0x4ced0a] 24: /usr/bin/Xorg (0x400000+0xd02e8) [0x4d02e8] 25: /usr/bin/Xorg (0x400000+0x35c8e) [0x435c8e] 26: /usr/bin/Xorg (0x400000+0x39aaa) [0x439aaa] 27: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7fb78d611000] 28: /usr/bin/Xorg (0x400000+0x2507e) [0x42507e] -- You are receiving this mail because: You are the assignee for the bug.

1 25

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2014