dri-devel January 2016

dri-devel@lists.freedesktop.org

194 participants
1200 discussions

[Bug 64201] New: OpenCL usage result segmentation fault on r600g with HD6850.
by bugzilla-daemon＠freedesktop.org 22 Mar '17

22 Mar '17

https://bugs.freedesktop.org/show_bug.cgi?id=64201 Priority: medium Bug ID: 64201 Assignee: dri-devel(a)lists.freedesktop.org Summary: OpenCL usage result segmentation fault on r600g with HD6850. Severity: normal Classification: Unclassified OS: other Reporter: spamjunkeater(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa I am using OpenSUSE 12.3 x86_64 with 3.9 Kernel and ATI 6850HD GPU. I just experiment OpenCL but I cannot make it with open source tools. compiled llvm, clang with : ./configure --libdir=/usr/lib64 --prefix=/usr --enable-{optimized,pic,shared} --disable-{assertions,docs,timestamps} --enable-targets="x86_64" --enable-experimental-targets="R600" (for llvm compilation, used http://llvm.org/docs/GettingStarted.html) And after, compiled mesa-trunk with ./configure --with-gallium-drivers=r600 --prefix=/usr --libdir=/usr/lib64 --enable-{vdpau,texture-float} --with-dri-drivers="" --enable-{gallium-llvm,r600-llvm-compiler,opencl} --enable-glx-tls --enable-shared-{glapi,dricore} but every utility that I tried, gives a segmentation error to me :-/ [ 3453.462803] python[7401]: segfault at 60 ip 00007f55c16292c0 sp 00007fff191b9138 error 4 in pipe_r600.so[7f55c14c0000+299000] [ 3465.707476] pyrit[7529]: segfault at 0 ip 00007f53614fb7cb sp 00007f535f2bc5c0 error 6 in libLLVM-3.3svn.so[7f5360eb1000+1004000] [ 3674.192257] cgminer[8773]: segfault at 20 ip 00007f2b65088710 sp 00007fffc1f24908 error 4 in libLLVM-3.3svn.so[7f2b648af000+1004000] Most detailed report from pyrit, by using it with benchmark argument; > pyrit benchmark Pyrit 0.4.1-dev (svn r308) (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com This code is distributed under the GNU General Public License v3+ Calibrating... 0x7faf109a72e0: i32 = GlobalAddress<i32 (i32, i32, i32)* @llvm.AMDGPU.bit.extract.u32.> 0 Undefined function UNREACHABLE executed at /run/media/death/OldRoot/temp/llvm/lib/Target/R600/AMDGPUISelLowering.h:56! Stack dump: 0. Running pass 'Function Pass Manager' on module 'radeon'. 1. Running pass 'AMDGPU DAG->DAG Pattern Instruction Selection' on function '@sha1_process' Aborted Regards, Erdem -- You are receiving this mail because: You are the assignee for the bug.

1 62

[Bug 64776] New: [9.1.2]"GPU fault detected" whit "eclipse juno" crash system
by bugzilla-daemon＠freedesktop.org 17 Mar '17

17 Mar '17

https://bugs.freedesktop.org/show_bug.cgi?id=64776 Priority: medium Bug ID: 64776 Assignee: dri-devel(a)lists.freedesktop.org Summary: [9.1.2]"GPU fault detected" whit "eclipse juno" crash system Severity: normal Classification: Unclassified OS: All Reporter: mombelli.mauro(a)gmail.com Hardware: Other Status: NEW Version: 9.1 Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 79557 --> https://bugs.freedesktop.org/attachment.cgi?id=79557&action=edit dmesg with a nice error log hi, after updating to mesa, ati-dri and mesa-libgl 9.1.2, everything work but when launching "eclipse juno" (even a fresh install) the monitor turn off, sometimes the system doesn't respond, sometimes the montor keep turning on and off, GUI in freezed but i can still use virtual consolle. No problem with steam, bzflag, flash, older version of eclipse or other java program. Also GPU extensive test have been done on windows system with no fault. Work-around is falling back to 9.1.1 my board: $ lspci | grep -i VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] here you will find attached dmesg and xorg log during one of the (rare) times when monitor was going on and off. Xorg seems to stop just before the system goes in this "loop state" anyway dmesg seems to catch the problem -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 84663] New: high cpu usage, poor performance in Borderlands 2 with radeonsi, PRIME
by bugzilla-daemon＠freedesktop.org 13 Mar '17

13 Mar '17

https://bugs.freedesktop.org/show_bug.cgi?id=84663 Bug ID: 84663 Summary: high cpu usage, poor performance in Borderlands 2 with radeonsi, PRIME 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: haagch(a)frickel.club Created attachment 107328 --> https://bugs.freedesktop.org/attachment.cgi?id=107328&action=edit sysprof recording from borderlands 2 only 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] (rev ff) xorg stable, mesa git, linux 3.17-rc7. I have had something similar in some games I think, but most recently with Borderlands 2. Here is a random screenshot with the HUD fps display from someone with a HD 7870 that shows that it runs mostly with 60 fps: https://i.imgur.com/qH0sBkl.jpg And here is a short clip of how it runs for me that shows it runs with 20-30 fps: https://www.youtube.com/watch?v=ZeZreRntt3k Radeontop says that the gpu is only used to ~30%. While running Borderlands 2 the CPU usage is always at 100+% on my i7 3632qm. I was undecided whether to report this here, but the difference is quite large so I thought I'd give it a try because I think the game itself is not supposed to use this much cpu time, so maybe it has something to do with the driver. Theories: < glennk> guessing from that output that the game engine uses a lot of occlusion queries and is stalling on them I haven't really found anything to test that yet. < agd5f> haagch, hybrid laptops have to do a lot of extra copying to get the frame from the rendering GPU to the display GPU I hope that the overhead is not *that* large because losing 70+% of gpu time would make it kind of useless for the affected games. Fortunately many (most?) games run much better, for example unigine valley shows good gpu usage: https://www.youtube.com/watch?v=sLWvYJlfvWM which makes me believe that there is a specific bottleneck. Attached is a sysprof profile of borderlands 2 but I don't know which of it is normal (like 25% total cpu time for glDrawRangeElements?). -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 76490] New: No output after radeon module is loaded (R9 270X)
by bugzilla-daemon＠freedesktop.org 13 Mar '17

13 Mar '17

https://bugs.freedesktop.org/show_bug.cgi?id=76490 Priority: medium Bug ID: 76490 Assignee: dri-devel(a)lists.freedesktop.org Summary: No output after radeon module is loaded (R9 270X) Severity: normal Classification: Unclassified OS: All Reporter: mail(a)geleia.net Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 96217 --> https://bugs.freedesktop.org/attachment.cgi?id=96217&action=edit kernel log The screen goes black after the radeon module is loaded. The only way I can get any output is to blacklist the radeon module, load it via modprobe and then change the resolution with xrandr from another computer via ssh. I seem to get some sort of lockup if I don't blacklist the module, because then I get a black screen at startup and I cannot even ssh into the machine. I tried to enable netconsole from the kernel command line but I can't get it to work (do I have to compile it statically?). I tried this with 3.14-rc6. For reference, I'm including the log output I get after I load the radeon module. This card is an MSI R9 270X Gaming 4G. -- You are receiving this mail because: You are the assignee for the bug.

1 126

[Bug 37724] New: occlusion queries are messed up in ut2004 (regression, bisected)
by bugzilla-daemon＠freedesktop.org 11 Mar '17

11 Mar '17

https://bugs.freedesktop.org/show_bug.cgi?id=37724 Summary: occlusion queries are messed up in ut2004 (regression, bisected) Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aaalmosss(a)gmail.com The majority of the 3d objects disappear periodically since this commit: f76787b3eae3f0b8af839fabfb24b57715a017f6 is the first bad commit commit f76787b3eae3f0b8af839fabfb24b57715a017f6 Author: Marek Olšák <maraeo(a)gmail.com> Date: Sun May 29 04:36:36 2011 +0200 r300g: fix occlusion queries when depth test is disabled or zbuffer is missing From now on, depth test is always enabled in hardware. If depth test is disabled in Gallium, the hardware Z function is set to ALWAYS. If there is no zbuffer set, the colorbuffer0 memory is set as a zbuffer to silence the CS checker. This fixes piglit: - occlusion-query-discard - NV_conditional_render/bitmap - NV_conditional_render/drawpixels - NV_conditional_render/vertex_array :040000 040000 baeff41ffed8952cbb1666d04941c6d5d01ca4fc cdb64f4b684804b818df4b65c04109eaad568e11 M src -- 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 93687] ppc64el:Gallium / clover fails to compile
by bugzilla-daemon＠freedesktop.org 07 Mar '17

07 Mar '17

https://bugs.freedesktop.org/show_bug.cgi?id=93687 Bug ID: 93687 Summary: ppc64el:Gallium / clover fails to compile Product: Mesa Version: 11.0 Hardware: PowerPC OS: All Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: kb9vqf(a)pearsoncomputing.net QA Contact: dri-devel(a)lists.freedesktop.org Gallium fails to compile on ppc64el. This prevens the use of the R600 OpenCL driver on the ppc64el platform. Full log: https://librarian.quickbuild.pearsoncomputing.net/7108453/buildlog_ubuntu-s… Relevant snippet: /bin/bash ../../../../libtool --tag=CXX --mode=compile g++ -DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.8\" -DPACKAGE_STRING=\"Mesa\ 11.0.8\" -DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\" -DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.8\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1 -DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1 -DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1 -DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1 -DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1 -DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1 -DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1 -DHAVE_FUNC_ATTRIBUTE_PACKED=1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1 -DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1 -DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../../../src/gallium/state_trackers/clover -DHAVE_PIPE_LOADER_DRI -DHAVE_PIPE_LOADER_DRM -DPIPE_SEARCH_DIR=\"/usr/lib/powerpc64le-linux-gnu/gallium-pipe\" -I../../../../../../include -I../../../../../../src -I../../../../../../src/gallium/include -I../../../../../../src/gallium/drivers -I../../../../../../src/gallium/auxiliary -I../../../../../../src/gallium/winsys -I../../../../../../src/gallium/state_trackers/clover -DHAVE_CLOVER_ICD -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fvisibility=hidden -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall -fno-strict-aliasing -fno-builtin-memcmp -MT api/libclover_la-program.lo -MD -MP -MF api/.deps/libclover_la-program.Tpo -c -o api/libclover_la-program.lo `test -f 'api/program.cpp' || echo '../../../../../../src/gallium/state_trackers/clover/'`api/program.cpp libtool: compile: g++ -DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.8\" "-DPACKAGE_STRING=\"Mesa 11.0.8\"" "-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa\"" -DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.8\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1 -DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1 -DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1 -DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1 -DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1 -DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1 -DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1 -DHAVE_FUNC_ATTRIBUTE_PACKED=1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1 -DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1 -DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../../../src/gallium/state_trackers/clover -DHAVE_PIPE_LOADER_DRI -DHAVE_PIPE_LOADER_DRM -DPIPE_SEARCH_DIR=\"/usr/lib/powerpc64le-linux-gnu/gallium-pipe\" -I../../../../../../include -I../../../../../../src -I../../../../../../src/gallium/include -I../../../../../../src/gallium/drivers -I../../../../../../src/gallium/auxiliary -I../../../../../../src/gallium/winsys -I../../../../../../src/gallium/state_trackers/clover -DHAVE_CLOVER_ICD -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fvisibility=hidden -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall -fno-strict-aliasing -fno-builtin-memcmp -MT api/libclover_la-program.lo -MD -MP -MF api/.deps/libclover_la-program.Tpo -c ../../../../../../src/gallium/state_trackers/clover/api/program.cpp -fPIC -DPIC -o api/.libs/libclover_la-program.o In file included from /usr/include/c++/5/map:60:0, from ../../../../../../src/gallium/state_trackers/clover/core/property.hpp:26, from ../../../../../../src/gallium/state_trackers/clover/api/util.hpp:30, from ../../../../../../src/gallium/state_trackers/clover/api/context.cpp:23: /usr/include/c++/5/bits/stl_tree.h: In constructor 'std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_Rb_tree(std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>&&, std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_Node_allocator&&)': /usr/include/c++/5/bits/stl_tree.h:1332:76: error: '__vector(4) __bool int' is not a valid type for a template non-type parameter using __eq = integral_constant<bool, _Alloc_traits::_S_always_equal()>; ^ /usr/include/c++/5/bits/stl_tree.h:1334:25: error: there are no arguments to '__eq' that depend on a template parameter, so a declaration of '__eq' must be available [-fpermissive] _M_move_data(__x, __eq()); ^ /usr/include/c++/5/bits/stl_tree.h:1334:25: note: (if you use '-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated) -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 105581] New: amdgpu: r9 380 Dual Monitor Setup: rotation not working
by bugzilla-daemon＠bugzilla.kernel.org 06 Mar '17

06 Mar '17

https://bugzilla.kernel.org/show_bug.cgi?id=105581 Bug ID: 105581 Summary: amdgpu: r9 380 Dual Monitor Setup: rotation not working Product: Drivers Version: 2.5 Kernel Version: 4.2.2, 4.3-rc3, 4.3-rc4 Hardware: Intel 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: f.otti(a)gmx.at Regression: No Created attachment 189561 --> https://bugzilla.kernel.org/attachment.cgi?id=189561&action=edit Xorg log of 4.3.rc3 Lengthy explanation posted here: https://forums.gentoo.org/viewtopic-p-7824374.html Dual Monitor setup doesn't seem to work at all when both are connected via DVI. When one is connected to HDMI and the other to the first DVI, dual monitor only works when one of them is connected after boot. Both only work when one is connected to HDMI and the other to the second DVI. With neither configuration does rotating any screen work. Results in crash of the X server (attachment). Everything works as intended under Windows. What I mean with "dual monitor is not working" is that both screens are recognized as connected but one of the screens shows only a black picture, but I can move applications to it (which I can't see). Steps to reproduce: Boot computer and try to rotate one of the screens with the KDE system settings or xrandr. -- You are receiving this mail because: You are watching the assignee of the bug.

1 4

[Bug 95771] New: Crash when trying to hibernate
by bugzilla-daemon＠bugzilla.kernel.org 06 Mar '17

06 Mar '17

https://bugzilla.kernel.org/show_bug.cgi?id=95771 Bug ID: 95771 Summary: Crash when trying to hibernate Product: Drivers Version: 2.5 Kernel Version: 3.19.3 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: higuita(a)gmx.net Regression: No I usually hibernate my machine and sometimes it looks like it hibernates, but fail to shutdown the machine... on next boot i found that the hibernation failled as the machine start up normally I finally got a usb-serial cable to connect this computer to another and manage to log this via serial port when the hibernation fail: [ 6500.667464] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 [ 6500.667481] IP: [<ffffffffa0360653>] radeon_vm_bo_invalidate+0x73/0xa0 [radeon] [ 6500.667483] PGD 864dc067 PUD 864dd067 PMD 0 [ 6500.667485] Oops: 0002 [#1] SMP [ 6500.667508] Modules linked in: usb_storage cpufreq_conservative ipt_ECN snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 ip6table_mangle ip6table_filter ip6_tables xt_DSCP nf_nat_irc nf_nat nf_conntrack_irc nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack nf_log_ipv4 nf_log_common xt_LOG xt_limit ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_mangle iptable_filter ip_tables x_tables bridge stp llc ipv6 sch_fq_codel pcspkr fuse joydev hid_generic snd_hda_codec_realtek snd_hda_codec_generic tuner_xc2028 dib7000p dvb_usb_dib0700 dib7000m dib0090 dib0070 dib3000mc dibx000_common dvb_usb dvb_core usbhid hid eeepc_wmi asus_wmi sparse_keymap rfkill i2c_dev acpi_cpufreq snd_hda_codec_hdmi tuner_simple tuner_types tea5767 tuner tda7432 tvaudio msp3400 crc32_pclmul crc32c_intel snd_hda_intel ghash_clmulni_intel snd_hda_controller amdkfd amd_iommu_v2 ohci_pci ohci_hcd bttv btcx_risc tveeprom videobuf_dma_sg rc_core radeon v4l2_common snd_hda_codec snd_bt87x fam15h_power k10temp snd_pcm r8169 videodev evdev snd_timer xhci_pci edac_core ehci_pci drm_kms_helper videobuf_core mii microcode xhci_hcd ttm ehci_hcd i2c_piix4 wmi snd parport_pc soundcore parport video processor thermal_sys button loop [last unloaded: lz4_compress] [ 6500.667526] CPU: 2 PID: 5386 Comm: SteamChildMonit Tainted: G W 3.19.3-slack #18 [ 6500.667526] Hardware name: System manufacturer System Product Name/A88X-PLUS, BIOS 2202 01/19/2015 [ 6500.667527] task: ffff8801d630dac0 ti: ffff8800817ec000 task.ti: ffff8800817ec000 [ 6500.667541] RIP: 0010:[<ffffffffa0360653>] [<ffffffffa0360653>] radeon_vm_bo_invalidate+0x73/0xa0 [radeon] [ 6500.667542] RSP: 0000:ffff8800817efa68 EFLAGS: 00010246 [ 6500.667543] RAX: ffff8800989ae600 RBX: ffff8801d60a5480 RCX: 0000000000000000 [ 6500.667544] RDX: ffff8801d60a54e0 RSI: ffff8801d4e59400 RDI: ffff8800989ae630 [ 6500.667545] RBP: ffff8801d4e596a8 R08: ffff8801d4fad178 R09: 0000000100400028 [ 6500.667545] R10: ffffea0007bc99c0 R11: ffffffff8171ff65 R12: ffff8801d4e59400 [ 6500.667546] R13: ffff880212864710 R14: 000000000000005e R15: ffff8801d4e59468 [ 6500.667548] FS: 00007fa35204c7c0(0000) GS:ffff88021ed00000(0000) knlGS:00000000ef83fb40 [ 6500.667549] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 [ 6500.667550] CR2: 0000000000000008 CR3: 00000000864db000 CR4: 00000000000407e0 [ 6500.667550] Stack: [ 6500.667552] ffff8801d4e59468 ffff8801d4e59468 0000000000000000 ffffffffa029a0dd [ 6500.667554] ffff8801d4e59468 0000000000000002 ffff880213f0b300 ffffffffa00ea2de [ 6500.667555] ffff8801d4e59498 ffffffffa00eb3b3 0000000000012540 ffff8800817efb20 [ 6500.667556] Call Trace: [ 6500.667571] [<ffffffffa029a0dd>] ? radeon_bo_move_notify+0x5d/0xb0 [radeon] [ 6500.667579] [<ffffffffa00ea2de>] ? ttm_bo_cleanup_memtype_use+0x1e/0x80 [ttm] [ 6500.667587] [<ffffffffa00eb3b3>] ? ttm_bo_release+0x1f3/0x2c0 [ttm] [ 6500.667590] [<ffffffff81706a40>] ? drm_gem_dumb_destroy+0x20/0x20 [ 6500.667604] [<ffffffffa0299408>] ? radeon_bo_unref+0x28/0x50 [radeon] [ 6500.667620] [<ffffffffa02adf2a>] ? radeon_gem_object_free+0x3a/0x40 [radeon] [ 6500.667623] [<ffffffff817068db>] ? drm_gem_object_handle_unreference_unlocked+0xdb/0x110 [ 6500.667625] [<ffffffff81706a9d>] ? drm_gem_object_release_handle+0x5d/0x90 [ 6500.667627] [<ffffffff8161ab83>] ? idr_for_each+0xa3/0xf0 [ 6500.667630] [<ffffffff81994e6e>] ? mutex_lock+0xe/0x2a [ 6500.667632] [<ffffffff817072dc>] ? drm_gem_release+0x1c/0x30 [ 6500.667635] [<ffffffff81706093>] ? drm_release+0x403/0x4f0 [ 6500.667637] [<ffffffff811a2d33>] ? __fput+0xe3/0x200 [ 6500.667640] [<ffffffff8109995c>] ? task_work_run+0xcc/0xf0 [ 6500.667643] [<ffffffff810808ac>] ? do_exit+0x2dc/0xaf0 [ 6500.667644] [<ffffffff810017f9>] ? __switch_to+0x449/0x520 [ 6500.667647] [<ffffffff81081ebd>] ? do_group_exit+0x3d/0xa0 [ 6500.667649] [<ffffffff8108cd94>] ? get_signal+0x1b4/0x5c0 [ 6500.667651] [<ffffffff810b86fe>] ? remove_wait_queue+0x1e/0x70 [ 6500.667654] [<ffffffff81002309>] ? do_signal+0x49/0xa20 [ 6500.667656] [<ffffffff810800b0>] ? task_stopped_code+0x50/0x50 [ 6500.667659] [<ffffffff810f91b7>] ? C_SYSC_wait4+0xf7/0x100 [ 6500.667660] [<ffffffff810a7d9d>] ? wake_up_new_task+0xed/0x190 [ 6500.667663] [<ffffffff81002d3d>] ? do_notify_resume+0x5d/0x80 [ 6500.667665] [<ffffffff81996e27>] ? int_signal+0x12/0x17 [ 6500.667683] Code: 48 89 10 48 b8 00 01 10 00 00 00 ad de 48 89 43 60 48 b8 00 02 20 00 00 00 ad de 48 8d 53 60 48 89 43 68 48 8b 43 70 48 8b 48 38 <48> 89 51 08 48 89 4b 60 48 8d 48 38 48 89 4b 68 48 89 50 38 48 [ 6500.667696] RIP [<ffffffffa0360653>] radeon_vm_bo_invalidate+0x73/0xa0 [radeon] [ 6500.667697] RSP <ffff8800817efa68> [ 6500.667698] CR2: 0000000000000008 [ 6500.667699] ---[ end trace 595ff6f3d8afbf5b ]--- [ 6500.667700] Fixing recursive fault but reboot is needed! [ 6511.926155] eth0: port 1(peth0) entered forwarding state [ 7247.320362] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [ 7247.339662] ata6.00: waking up from sleep [ 7247.351674] ata6: hard resetting link [ 7248.077942] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 7248.101388] ata6.00: configured for UDMA/100 [ 7248.114184] ata6: EH complete So after this, i don't have a working nor a hibernated machine I'm using slackwre64-current, in a A10-7850k CPU and a Asus A88X-plus -- You are receiving this mail because: You are watching the assignee of the bug.

1 6

[Bug 89785] GPU Fault 147 and Ring Stalls and Tests Fail in Pillars of Eternity
by bugzilla-daemon＠freedesktop.org 15 Feb '17

15 Feb '17

https://bugs.freedesktop.org/show_bug.cgi?id=89785 Bug ID: 89785 Summary: GPU Fault 147 and Ring Stalls and Tests Fail in Pillars of Eternity Product: Mesa Version: 10.5 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: matt.scheirer(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 114656 --> https://bugs.freedesktop.org/attachment.cgi?id=114656&action=edit Kernel log of GPU Hang On my r9 290 GPU, the newly released Pillars of Eternity causes a GPU fault and kernel panic on 10.5.1. Works fine with an Intel part. Requires a REISUB to reset the system every time. Attached is the kernel log of the crashing behavior - it is reproducible every time I run the game as soon as it hits a loading screen. Kernel is 3.19.2. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 93247] Bound by Flame game crashes GPU
by bugzilla-daemon＠freedesktop.org 15 Feb '17

15 Feb '17

https://bugs.freedesktop.org/show_bug.cgi?id=93247 Bug ID: 93247 Summary: Bound by Flame game crashes GPU Product: Mesa Version: 11.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: l.gambetta(a)alice.it QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 120332 --> https://bugs.freedesktop.org/attachment.cgi?id=120332&action=edit Messages printed into the journalctl log about this crash I'm trying to run this newly released game ( http://store.steampowered.com/app/243930/ ) on this PC: CPU AMD A10-7850K, 8 GB Ram ATI Radeon 7850 1Gb Mesa 11.0.6 xf86-video-ati 7.5.0 linux kernel 4.2.6 Distro is Manjaro Linux. The game is 32 bit and I'm using native 32 bit libraries instead of the ones supplied by the Steam SDK. The game crashes on the loading screen after the "start game" and intro sequence. I had to reset my PC. -- 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 January 2016