dri-devel June 2015

dri-devel@lists.freedesktop.org

188 participants
1140 discussions

[Bug 67849] New: continuos reboots
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=67849 Priority: medium Bug ID: 67849 Assignee: dri-devel(a)lists.freedesktop.org Summary: continuos reboots Severity: critical Classification: Unclassified OS: Linux (All) Reporter: markurujapan(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/Radeon Product: Mesa I can't use opensource drivers with my apu a8 5600k(radeon 7650d) on linux. I tried with linux kernel 3.10, 3.11 rc, mesa, mesa git, xf86 ati, git..etc. The problem persist, every 20/30 minutes my apu suddenly reboot, it's so strange, because this doesn't happen with catalyst driver( but closed driver is so slow for me..). I don't know what is the origin of the problem. :( -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 67724] New: [r600g] WoW slowdown with HD6450
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=67724 Priority: medium Bug ID: 67724 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] WoW slowdown with HD6450 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: rankincj(a)googlemail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Playing WoW with Mesa-git recently, and I discovered that the frame rate had dropped by ~10 FPS. (From 25 FPS to 15 FPS). A git bisect identifies this commit: $ git bisect bad 6a2baf3a06125405aa648e208af782e53f1312c0 is the first bad commit commit 6a2baf3a06125405aa648e208af782e53f1312c0 Author: Paul Berry <stereotype441(a)gmail.com> Date: Mon Jun 10 14:01:45 2013 -0700 glsl/linker: Make update_array_sizes apply to just uniforms. Commit 586b4b5 (glsl: Also update implicit sizes of varyings at link time) extended update_array_sizes() to apply to both uniforms and shader ins/outs. However, doing creates problems for geometry shaders, because update_array_sizes() assumes that variables with matching names in different parts of the pipeline should have the same sizes. With the addition of geometry shaders, this is no longer true (e.g. both vertex and geometry shaders have a gl_ClipDistance output variable, but there's no reason these variables should have the same sizes). The original reason for commit 586b4b5 (avoid problems with gl_TexCoord being 0 length) has since been addressed by commit 6f53921 (linker: Ensure that unsized arrays have a size after linking). So go ahead and switch update_array_sizes() back to only acting on uniforms. Reviewed-by: Ian Romanick <ian.d.romanick(a)intel.com> Reviewed-by: Kenneth Graunke <kenneth(a)whitecape.org> :040000 040000 304adffc0a8c034063a526a7d693fe792399a7d9 77b9d43aacde4ec2172578b7158399d94f6e3b2e M src -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 67265] New: r600g causes KWin crashes with kernel 3.9
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=67265 Priority: medium Bug ID: 67265 Assignee: dri-devel(a)lists.freedesktop.org Summary: r600g causes KWin crashes with kernel 3.9 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: nikoli(a)lavabit.com Hardware: x86-64 (AMD64) Status: NEW Version: 9.1 Component: Drivers/Gallium/r600 Product: Mesa With FOSS radeon driver kwin crashes after unlocking session when it was locked for several (8-10) hours. If it was locked only for several minutes it will not crash. Sometimes it does not crash even when locked for hours. No 3D apps are working until X is restarted. https://bugs.kde.org/show_bug.cgi?id=322773 Versions: [ebuild R ~] media-libs/mesa-9.1.4 USE="egl gallium gbm gles2 nptl openvg pax_kernel shared-glapi wayland xa xorg -bindist -classic -debug -gles1 -llvm -osmesa -pic (-r600-llvm-compiler) (-selinux) -vdpau -xvmc" PYTHON_SINGLE_TARGET="python2_7 -python2_6" PYTHON_TARGETS="python2_7 -python2_6" VIDEO_CARDS="r600 radeon -i915 -i965 -intel -nouveau -r100 -r200 -r300 (-radeonsi) -vmware" 0 kB [ebuild R ] x11-libs/libdrm-2.4.45 USE="libkms -static-libs" VIDEO_CARDS="radeon (-exynos) (-freedreno) -intel -nouveau (-omap) -vmware" 0 kB [ebuild R ] x11-base/xorg-server-1.13.4:0/1.13.4 USE="ipv6 nptl suid udev xorg xvfb -dmx -doc -kdrive -minimal (-selinux) -static-libs -tslib -xnest" 0 kB [ebuild R ] kde-base/kwin-4.10.4:4 USE="opengl (-aqua) -debug -gles" 0 kB [ebuild R ~] x11-drivers/xf86-video-ati-7.1.0 USE="udev -glamor" 0 kB [ebuild R ] dev-qt/qtgui-4.8.4-r1:4 USE="accessibility cups dbus exceptions gif glib mng qt3support tiff xinerama xv (-aqua) -c++0x -debug -egl -gtkstyle -nas -nis (-pch) -trace" 0 kB -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 67016] New: Lockup on piglit test vs-textureSize-compare with AMD 6950
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=67016 Priority: medium Bug ID: 67016 Assignee: dri-devel(a)lists.freedesktop.org Summary: Lockup on piglit test vs-textureSize-compare with AMD 6950 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: g02maran(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI I'm running kernel http://cgit.freedesktop.org/~agd5f/linux/?h=drm-fixes-3.11 with latest commit 444bddc4b9b3313a562cd3ba40f780fb82570f7d and mesa master with latest commit e4fdf1b008ce29c5b5a52985c586b61f35d31e4c When I run spec/glsl-1.30/execution/vs-textureSize-compare my system locks up. I can't reboot or ssh into it, I have the power cycle the machine to reset it. Nothing is printed to dmesg before it hangs. I have tried both with and without radeon.dpm=1, no difference. I did a bisect and it identified this commit: http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3.11&id=1c0110… -- You are receiving this mail because: You are the assignee for the bug.

1 19

[Bug 66964] New: GPU fault detected
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=66964 Priority: medium Bug ID: 66964 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU fault detected Severity: normal Classification: Unclassified OS: All Reporter: udovdh(a)xs4all.nl Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Hello, See https://bugs.freedesktop.org/show_bug.cgi?id=62959 as reference. I turned off RADEON_VA=0 and R600_DEBUG=nodma and after a while I got the output below (and a reboot) while surfing the web, checking videos from youtube, etc. I use git everything on A10-5800K which has ARUBA (Cayman) GPU with kernel.org 3.9.9. What is the cause? And how can we fix this? Jul 16 16:00:01 surfplank2 kernel: [178650.498628] radeon 0000:00:01.0: GPU fault detected: 147 0x0db67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498633] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00001EDB Jul 16 16:00:01 surfplank2 kernel: [178650.498635] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x06071002 Jul 16 16:00:01 surfplank2 kernel: [178650.498638] radeon 0000:00:01.0: GPU fault detected: 147 0x0db67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498640] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498643] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498645] radeon 0000:00:01.0: GPU fault detected: 146 0x01f67104 Jul 16 16:00:01 surfplank2 kernel: [178650.498647] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498649] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498652] radeon 0000:00:01.0: GPU fault detected: 146 0x02067104 Jul 16 16:00:01 surfplank2 kernel: [178650.498654] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498656] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498658] radeon 0000:00:01.0: GPU fault detected: 146 0x02067104 Jul 16 16:00:01 surfplank2 kernel: [178650.498660] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498662] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498664] radeon 0000:00:01.0: GPU fault detected: 147 0x03b67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498667] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498669] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498671] radeon 0000:00:01.0: GPU fault detected: 147 0x03c67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498673] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498675] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498677] radeon 0000:00:01.0: GPU fault detected: 147 0x03c67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498679] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498681] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498683] radeon 0000:00:01.0: GPU fault detected: 147 0x03c67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498685] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498687] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498690] radeon 0000:00:01.0: GPU fault detected: 146 0x02067104 Jul 16 16:00:01 surfplank2 kernel: [178650.498692] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498694] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x06071004 Jul 16 16:00:01 surfplank2 kernel: [178650.498711] radeon 0000:00:01.0: GPU fault detected: 146 0x09767104 Jul 16 16:00:01 surfplank2 kernel: [178650.498713] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498715] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Kind regards, Udo -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 66961] New: Kernel BUG/Oops during radeon gpu stall
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=66961 Priority: medium Bug ID: 66961 Assignee: dri-devel(a)lists.freedesktop.org Summary: Kernel BUG/Oops during radeon gpu stall Severity: normal Classification: Unclassified OS: Linux (All) Reporter: knut.tidemann(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 82479 --> https://bugs.freedesktop.org/attachment.cgi?id=82479&action=edit dmesg output I've noticed a kernel BUG/Oops during a GPU stall when playing Legend of Grimrock (closed source). The oops causes X to become a defunct process with no entires in the Xorg.log file. The screen goes into standby mode and the only way to solve this is to reboot the computer. The machine is responsive via ssh and I've attached my dmesg output after the oops. I have not played this game with another kernel, so I don't know if it's new or not. I have a Radeon HD 4850, on an Intel Core2Duo with 8GB of ram. Running 'latest' git (gb616d01). -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 66920] New: [llvm backend] flashing textures, no lights in car , no water on GTA IV
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=66920 Priority: medium Bug ID: 66920 Assignee: dri-devel(a)lists.freedesktop.org Summary: [llvm backend] flashing textures, no lights in car , no water on GTA IV Severity: normal Classification: Unclassified OS: Linux (All) Reporter: son_of_the_osiris(a)interia.pl Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa I just tried sb backend with GTA IV on wine and must say that it works better than llvm. With llvm I have black rectangle instead of car lights and same with water. Also I seen some flashing textures.When enable R600_DEBUG-sb,nollvm game run little faster and without graphics problem. Kernel 3.10 wine 1.6rc5 mesa - git compiled with : --prefix=/usr \ --sysconfdir=/etc \ --with-dri-driverdir=/usr/lib/xorg/modules/dri \ --with-gallium-drivers=r600 \ --with-dri-drivers= \ --with-llvm-shared-libs \ --enable-gallium-llvm \ --enable-r600-llvm-compiler \ --enable-xvmc \ --enable-egl \ --enable-gallium-egl \ --with-egl-platforms=x11,drm,wayland \ --enable-shared-glapi \ --enable-gbm \ --enable-glx-tls \ --enable-opencl \ --disable-debug \ --disable-osmesa \ --enable-gles1 \ --enable-gles2 \ --enable-texture-float \ --disable-xa \ --enable-vdpau \ -- You are receiving this mail because: You are the assignee for the bug.

1 19

[Bug 66883] New: [r600 llvm backend] Assert with 32-bit lightsmark, TF2 when shader dump is enabled
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=66883 Priority: medium Bug ID: 66883 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600 llvm backend] Assert with 32-bit lightsmark, TF2 when shader dump is enabled Severity: normal Classification: Unclassified OS: All Reporter: ptpzz(a)yandex.ru Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa I have asserts in the middle of shader dump in llvm backend with 32-bit Team Fortress 2 and Lightsmark, R600_DEBUG=ps,vs. Here is message with Lightsmark: ... ALU_CLAUSE 8; dbg:backend: DebugLoc.cpp:27: llvm::MDNode* llvm::DebugLoc::getScope(const llvm::LLVMContext&) const: Assertion `unsigned(ScopeIdx) <= Ctx.pImpl->ScopeRecords.size() && "Invalid ScopeIdx!"' failed. TF2 message: ... ALU_CLAUSE 32; dbg:hl2_linux: DebugLoc.cpp:33: llvm::MDNode* llvm::DebugLoc::getScope(const llvm::LLVMContext&) const: Assertion `unsigned(-ScopeIdx) <= Ctx.pImpl->ScopeInlinedAtRecords.size() && "Invalid ScopeIdx"' failed. It seems in both cases it happens on ALU clause start in the dump. So far I can't reproduce this issue with 64-bit Lightsmark/mesa/llvm. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 66880] New: R600_DEBUG=sb hangs system after playing xonotic, spring
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=66880 Priority: medium Bug ID: 66880 Assignee: dri-devel(a)lists.freedesktop.org Summary: R600_DEBUG=sb hangs system after playing xonotic, spring Severity: normal Classification: Unclassified OS: Linux (All) Reporter: pheldens(a)ziggo.nl Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa linux 3.10.* and before R600_DEBUG=sb radeon 4670 crashes in xonotic and spring after indeterminate time, colours the screen with garbage, does not crash when R600_DEBUG is unset. all I caught so far is a kernel oops output Oops: 0000 [#1] PREEMPT SMP Modules linked in: snd_hda_codec_hdmi snd_cmipci snd_opl3_lib snd_mpu401_uart snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_hda_intel snd_hda_codec snd_hwdep CPU: 0 PID: 1539 Comm: X Not tainted 3.10.0-rc6 #2 Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7596/785GM-E51 (MS-7596), BIOS V2.11 12/08/2010 task: ffff88022e9f9320 ti: ffff880226ca4000 task.ti: ffff880226ca4000 RIP: 0010:[<ffffffff813e74ca>] [<ffffffff813e74ca>] radeon_fence_process+0x8a/0x150 RSP: 0018:ffff880226ca5c28 EFLAGS: 00010246 RAX: ffffc9001079c598 RBX: 0000000000000002 RCX: ffff880226972da0 RDX: 0000000000000041 RSI: 0000000000000000 RDI: ffff880226972000 RBP: 000000000000000c R08: ffff880226972208 R09: 0000000000000000 R10: 0000000000000005 R11: 0000000000000304 R12: ffff880226972df0 R13: 0000000000000002 R14: ffff880226972000 R15: ffffffff00000000 FS: 00007fe0a9315880(0000) GS:ffff88022fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: ffffc9001079c598 CR3: 00000002241b6000 CR4: 00000000000007f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Stack: ffff88022695ce00 ffffffff8144f257 0000000000000292 ffffffff81948957 ffff88022eb8b560 ffff880226972000 0000000000000005 ffff880226972000 ffff880226972e20 ffff8802269725f8 0000000000000000 ffffffff813e7fdb Call Trace: [<ffffffff8144f257>] ? __dev_printk+0x37/0xa0 [<ffffffff813e7fdb>] ? radeon_fence_count_emitted+0x1b/0x70 [<ffffffff813fd8cd>] ? radeon_ring_backup+0x3d/0x120 [<ffffffff813d3601>] ? radeon_gpu_reset+0x81/0x210 [<ffffffff813fc930>] ? radeon_gem_wait_idle_ioctl+0xd0/0xf0 [<ffffffff813b0250>] ? drm_ioctl+0x460/0x560 [<ffffffff813fc860>] ? radeon_gem_busy_ioctl+0x120/0x120 [<ffffffff8108e8a4>] ? signal_delivered+0x54/0x70 [<ffffffff8112657a>] ? do_vfs_ioctl+0x8a/0x500 [<ffffffff810a98ce>] ? vtime_account_user+0x6e/0x90 [<ffffffff81126a3d>] ? SyS_ioctl+0x4d/0xa0 [<ffffffff8176bf49>] ? tracesys+0xd0/0xd5 Code: 48 39 d0 73 53 48 89 c3 41 b9 01 00 00 00 41 80 be 58 16 00 00 00 4d 8b a8 e0 0b 00 00 48 8d 41 08 0f 84 86 00 00 00 48 8b 40 10 <8b> 00 48 89 da 89 c0 4c 21 fa 48 09 d0 48 39 c3 76 0c 4c 89 ea RIP [<ffffffff813e74ca>] radeon_fence_process+0x8a/0x150 RSP <ffff880226ca5c28> CR2: ffffc9001079c598 ---[ end trace 2b43f4717e08f222 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 66731] New: texture issues in xonotic with llvm+sb and offset mapping
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=66731 Priority: medium Bug ID: 66731 Assignee: dri-devel(a)lists.freedesktop.org Summary: texture issues in xonotic with llvm+sb and offset mapping Severity: minor Classification: Unclassified OS: Linux (All) Reporter: stefano.teso(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa To reproduce, use: - xonotic 0.7.0 at lowest detail, with only offset mapping turned on. - r600g from git, with SB backend and LLVM both turned on. Turning off either makes the bug disappear (although there are other issues, rensambling z fighting, when only llvm is enabled; not sure if they are related to offset mapping, I'll check later.) The issue is clearly visible by running any of the demos that come with xonotic. FWIW, other apps (glxgears, gnome-shell, etc.) work just fine. $gitgl glxinfo | grep str server glx vendor string: SGI server glx version string: 1.4 client glx vendor string: Mesa Project and SGI client glx version string: 1.4 OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD CEDAR OpenGL version string: 2.1 Mesa 9.2.0-devel (git-2923685) OpenGL shading language version string: 1.30 $ llvm-config --version 3.3 Tested with both stock 3.10 kernel from arch linux and the recent dpm-wip5 branch. Nothing suspicious in dmesg. May be related to #50230, which was closed as fixed. -- You are receiving this mail because: You are the assignee for the bug.

1 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2015