[Bug 97039] The Talos Principle and Serious Sam 3 GPU faults
https://bugs.freedesktop.org/show_bug.cgi?id=97039 --- Comment #4 from smoki --- No, still the same faults happens. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/cabe38ae/attachment.html>
[Bug 87682] Horizontal lines in radeon driver on kernel 3.15 and upwards
https://bugs.freedesktop.org/show_bug.cgi?id=87682 --- Comment #23 from Gilbert Smith --- (In reply to Thom from comment #21) > Gilbert, same with me, also ubuntu 14.04 -> 16.04. > > The patch is already in the 4.7+ kernel tree so it should be in the first > 4.7 kernel (pre) release. > > I'm not familiar with ubuntu's kernel policy and I also don't know anyone > who does but I guess that the 4.7 kernel will land in 16.10 or 17.04. > Best to ask the Ubuntu Kernelteam. Thank you for the informative information. I'll probably stay on the LTS 16.04 but as soon as I get wind of the release of kernel 4.7+ I will install it. I was able to get my system working properly by reverting to kernel 3.13.0-92-generic. Here' a link to a discussion I found that stated that users who upgraded may use older kernels from 12.04 and 14.04 on 16.04 even if not supported. http://askubuntu.com/questions/776910/install-old-kernel-in-ubuntu-16-04/801847#801847 -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/d0cbc97a/attachment.html>
[Bug 93649] [radeonsi] Graphics lockup while playing tf2
https://bugs.freedesktop.org/show_bug.cgi?id=93649 --- Comment #18 from AmarildoJr --- Yes, I would definitely test it for a long period, something like 16 hours hehehe. However, I can't do any besecting right now, I'm tremendously busy at the moment. Too bad there's not many Linux players with this problem, otherwise someone would have figured this out already. Cheers. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/3bb049e6/attachment.html>
[Bug 117591] amdgpu: Black screens on A10-8700P (Carrizo) + R7 M260/M265 (Topaz) Combo
https://bugzilla.kernel.org/show_bug.cgi?id=117591 --- Comment #12 from Thomas J. Moore --- (In reply to Michel Dänzer from comment #11) > Thomas, since your symptoms are different from Jani's, please file your own > report, preferably at > https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/AMDgpu . I have done as requested, but I still think this bug covers it. Basically it amounts to "Broken Carrizo+Topaz [on HP?] power management issues lead to black or flickering screen with amdgpu". Since my latest working solution (boot into X w/ power management enabled, then reboot with it disabled) does not involve playing with the crtc switch, I am even more convinced of this. The only part that isn't covered is the system hang when killing X with crtc 1 enabled, but that's not something I ever cared about, anyway. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 93649] [radeonsi] Graphics lockup while playing tf2
https://bugs.freedesktop.org/show_bug.cgi?id=93649 --- Comment #17 from Nicolai Hähnle --- Actually, if you could find a clear bisection result, that would be tremendously helpful and would probably lead to a fix. However, with this kind of bug you need to be extremely sure about what you're doing when bisecting. For example, if you know that the hang typically occurs after 10 minutes, then you should play for at least one hour (perhaps even longer) with each kernel. Otherwise, you might have just gotten lucky, and the bisect result would be worse than useless. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/66825a16/attachment.html>
[Bug 93649] [radeonsi] Graphics lockup while playing tf2
https://bugs.freedesktop.org/show_bug.cgi?id=93649 --- Comment #16 from AmarildoJr --- So there's a chance it won't be fixed at all? I was thinking about bisecting from version 3.16 (where I know it worked for me, on Debian Jessie) until ~4.1, but I don't have that kind of time right now. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/627dfedd/attachment-0001.html>
[Bug 93649] [radeonsi] Graphics lockup while playing tf2
https://bugs.freedesktop.org/show_bug.cgi?id=93649 --- Comment #15 from Nicolai Hähnle --- This is certainly a bug in our driver (unlike what was written on the Github tracker, a game *can* cause a hang e.g. by writing an infinite loop in a shader, but that seems exceedingly unlikely in the case of TF2). The problem with this particular bug is that it seems non-deterministic (i.e. not reliably reproducible), and that makes it hard to debug. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/32eb173f/attachment.html>
[Bug 93649] [radeonsi] Graphics lockup while playing tf2
https://bugs.freedesktop.org/show_bug.cgi?id=93649 AmarildoJr changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #14 from AmarildoJr --- Any chance VALVe introduced this? They won't admit it. https://github.com/ValveSoftware/steam-for-linux/issues/4409 The patches attatched here are present in Linux 4.6. I tested linux-git-4.7-rc7 with mesa-git-12.1 compiled against llvm-snv-3.9, and TF2 still crashes. Setting every graphical option to Low doesn't help. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/9156ebb7/attachment.html>
[Bug 97039] The Talos Principle and Serious Sam 3 GPU faults
https://bugs.freedesktop.org/show_bug.cgi?id=97039 --- Comment #3 from Nicolai Hähnle --- Created attachment 125277 --> https://bugs.freedesktop.org/attachment.cgi?id=125277&action=edit Likely fix - RW_BUFFERS pointer is not written for LS stage Could you please try whether the attached patch fixes the problem for you? -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/de2deaed/attachment.html>
[Bug 96908] [radeonsi] MSAA causes graphical artifacts
https://bugs.freedesktop.org/show_bug.cgi?id=96908 Nicolai Hähnle changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #10 from Nicolai Hähnle --- Mesa master commit f755da0f2f8609e603b50424aa254358eb72fa25 -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/efdccb73/attachment.html>
[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN
https://bugs.freedesktop.org/show_bug.cgi?id=96678 --- Comment #26 from Quentin Quaadgras --- I just by chance tried running awesomenauts through the command line again after updating to a recent daily build and the game is now running. It is still not running within the steam client but this is a good sign. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/7f3ca042/attachment-0001.html>
[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN
https://bugs.freedesktop.org/show_bug.cgi?id=96678 --- Comment #25 from Quentin Quaadgras --- Any conclusions on this? -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/7150207b/attachment.html>
[Bug 97059] Tahiti+DRI3+Unity+Blender corruption
https://bugs.freedesktop.org/show_bug.cgi?id=97059 --- Comment #2 from dave --- Hello, Sorry for not explaining the issue, I don't know how to edit the first comment. I have noticed a bug in the rendering of blender using Radeonsi drivers and dri3. This happens with different versions of blender also. I'm using padoka's PPA and ubuntu 16.04. more details in the First comment. If I am missing anything let me know and i will get more information. Thanks Dave -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/ae462cc4/attachment.html>
[Bug 97059] Tahiti+DRI3+Unity+Blender corruption
https://bugs.freedesktop.org/show_bug.cgi?id=97059 --- Comment #1 from dave --- Created attachment 125273 --> https://bugs.freedesktop.org/attachment.cgi?id=125273&action=edit lshw output -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/aa5228e1/attachment.html>
[Bug 97059] Tahiti+DRI3+Unity+Blender corruption
https://bugs.freedesktop.org/show_bug.cgi?id=97059 Bug ID: 97059 Summary: Tahiti+DRI3+Unity+Blender corruption Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel at lists.freedesktop.org Reporter: eunbolt at gmail.com QA Contact: dri-devel at lists.freedesktop.org Created attachment 125272 --> https://bugs.freedesktop.org/attachment.cgi?id=125272&action=edit Xorg.0.log output Here is a link to a video of the bug happening https://youtu.be/tMs4QSW0OmY -=glxinfo output=- client glx vendor string: Mesa Project and SGI OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.1.0-devel - padoka PPA OpenGL version string: 3.0 Mesa 12.1.0-devel - padoka PPA OpenGL ES profile version string: OpenGL ES 3.1 Mesa 12.1.0-devel - padoka PPA -=screenfetch output=- OS: Ubuntu 16.04 xenial Kernel: x86_64 Linux 4.7.0-040700rc5-generic Uptime: 5m Packages: 2937 Shell: bash 4.3.46 Resolution: 1920x1080 DE: Unity 7.4.0 WM: Compiz WM Theme: Ambiance Ambiance [GTK2] , Ambiance [GTK3] Icon Theme: ubuntu-mono-dark Font: Ubuntu 11 CPU: AMD Phenom II X4 965 @ 3.4GHz GPU: Gallium 0.4 on AMD TAHITI (DRM 2.45.0 / 4.7.0-040700rc5-generic, LLVM 4.0.0) RAM: 2129MiB / 16049MiB /var/log/Xorg.0.log output attached -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/112f7581/attachment.html>
[ANNOUNCE] libdrm 2.4.70
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Boll (6): radeon: Wire up radeon-symbol-check to make check automake: Don't include Android Makefiles in the release tarball virtgpu: Update kernel header automake: Include virtgpu_drm.h in the release tarball man: Fix typo radeon: Fix typo in stderr message Emil Velikov (2): tests/drmdevice: print out the full 'bus' and 'dev' strings tests/drmdevice: be move verbose when using open() Qiang Yu (2): drm: drmGetDevice return correct device on multi GPU setups drm: fix drmFreeDevices memory leak on multi GPU setups Rob Clark (24): freedreno: rework internal ring->emit_reloc_ring() freedreno: add simpler ring-reloc freedreno: split out fd_bo_cache freedreno: refactor bo-cache API freedreno: move bo-cache to it's own file freedreno: sync uapi freedreno: add madvise support freedreno: fix potential fd leak in error path freedreno: expose kernel driver version freedreno: support either coarse or fine-grained bucket sizes freedreno: ocd freedreno: fix potential leak at free freedreno/msm: use private bo-cache for ringbuffer bo's freedreno/msm: drop return from get_cmd() freedreno/msm: split out cmd buffer tracking from ring list: add first/last entry macros freedreno/msm: split out dump_submit() helper freedreno: support growable cmdstream buffers freedreno/msm: use hashtable to track bo idx freedreno: move legacy kgsl related README freedreno: fix distcheck errors freedreno: fix android build break freedreno: fix warnings Bump version for release git tag: libdrm-2.4.70 http://dri.freedesktop.org/libdrm/libdrm-2.4.70.tar.bz2 MD5: 920957cfe25a80efb02be9bd90bf3c1e libdrm-2.4.70.tar.bz2 SHA1: 136a581c9a081ac26804ae229d27094f29001a21 libdrm-2.4.70.tar.bz2 SHA256: b17d4b39ed97ca0e4cffa0db06ff609e617bac94646ec38e8e0579d530540e7b libdrm-2.4.70.tar.bz2 PGP: http://dri.freedesktop.org/libdrm/libdrm-2.4.70.tar.bz2.sig http://dri.freedesktop.org/libdrm/libdrm-2.4.70.tar.gz MD5: a8c275bce5f3d71a5ca25e8fb60df084 libdrm-2.4.70.tar.gz SHA1: de18aaf55e00e9a07f51d95855de48d0b3e6bd02 libdrm-2.4.70.tar.gz SHA256: 73615b9c1c4852e5ce045efa19c866e8df98e396b2443bf859eea05574ecb64f libdrm-2.4.70.tar.gz PGP: http://dri.freedesktop.org/libdrm/libdrm-2.4.70.tar.gz.sig -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJXk3KeAAoJEBkcm5BVIrBFqr4QAINZS7N7wf7Te0IGnchorfOb iLnxU4Pd9T7KuTBC7wdgO8Ra/eO/9mN3tK0GMqUdwd1ztIn4yGxc+F+0jqE81Kd4 4Hn4ICdLzVTH6y/A5jEKuLwByb02iOdzOIwSI1cUIcjsLOxG3ZtvEcBknyOd05Hf FTRUGofHokDHKMP3FnEj9Xm7XDBobYMhuN75sd/ZyTNb6aZgsTh852eg6+mtPZyT ny+OaTcOYLJOiWMSvVl+pmCn1binLIenAbmnwSKpdrzzcqOG2eyHUzemJSm0JIc5 MKbYN/X1G00Jwkjre3GvagxJ7WQg0hEr3GQNEizyoCY6efyEOqLFZBMsly4oIAcF F3ekaOw9+e7wS9m7E2HqIcj/mpUMbIZHf83ObQ3fKLwv2SfAB1/EJYPSZ1lOAdsh wpCZC3hzW3Hk+DnJh1mxnkiEKAvpRD0HjpR7Js1mdKAj0xS65Djmj5Sdm6d+38oP MVIhji8kv9HIPKgB3/6G1VYOBlbql6uzaAOIPeLhS0UiolpmzKnM0AgmHJJitazM gGeMVPqjahm09MAoyZg+Xio9knsLWW39EKh45S9IuI5LF1wL1IIy9vku4OVHzWEW u1juoBk3C57B7OrHLctTPECUvArY1smAUhu2XOWIjlutJHwvofOc75trPmztpwZD bcfLE6ix81xaF0i1m9dg =w/rL -END PGP SIGNATURE-
[Bug 94900] HD6950 GPU lockup loop with various steam games (octodad[always], saints row 4[always], dead island[always], grid autosport[sometimes])
https://bugs.freedesktop.org/show_bug.cgi?id=94900 Heiko changed: What|Removed |Added CC||lil_tux at web.de --- Comment #21 from Heiko --- Created attachment 125271 --> https://bugs.freedesktop.org/attachment.cgi?id=125271&action=edit Simple workaround 'Fixes' the octodad trace for me. That stops sb from using fold_assoc to fold ADD_INT(ADD_INT(x, 1), 2) for scalar registers. Problem is, that sb currently optimizes away the loop counter node, due to optimizing its reference out of another node and marking it as unused/dead, finally nuking the counter increment as well. Thus the loop break condition is never met and the gpu hangs due to an endless loop, and finally, gets reset. If mesa is compiled in debug mode, sb checks the shader it would put out and fails assertions with unset registers... just being the loop counter of the three loops in the octodad case (shader 70). On a side note, this scenario might be already known for phi nodes, as the comment in sb_expr.cpp:expr_handler::fold() mentions similar issues... -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/d30d87b6/attachment.html>
[PATCH v3 1/7] firmware: rockchip: sip: Add rockchip SIP runtime service
Hi, [auto build test ERROR on next-20160722] [also build test ERROR on v4.7-rc7] [cannot apply to rockchip/for-next stable/master linux/master v4.7-rc7 v4.7-rc6 v4.7-rc5] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Lin-Huang/rk3399-support-ddr-frequency-scaling/20160722-173343 config: arm64-allmodconfig (attached as .config) compiler: aarch64-linux-gnu-gcc (Debian 5.4.0-6) 5.4.0 20160609 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # save the attached .config to linux build tree make.cross ARCH=arm64 All errors (new ones prefixed by >>): drivers/built-in.o: In function `sip_smc_ddr_init': >> binder.c:(.text+0x279074): undefined reference to `__invoke_psci_fn_smc' drivers/built-in.o: In function `sip_smc_set_ddr_param': binder.c:(.text+0x2790ac): undefined reference to `__invoke_psci_fn_smc' drivers/built-in.o: In function `sip_smc_set_ddr_rate': binder.c:(.text+0x2790ec): undefined reference to `__invoke_psci_fn_smc' drivers/built-in.o: In function `sip_smc_get_ddr_rate': binder.c:(.text+0x279124): undefined reference to `__invoke_psci_fn_smc' drivers/built-in.o: In function `sip_smc_clr_ddr_irq': binder.c:(.text+0x279154): undefined reference to `__invoke_psci_fn_smc' drivers/built-in.o:binder.c:(.text+0x279184): more undefined references to `__invoke_psci_fn_smc' follow --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation -- next part -- A non-text attachment was scrubbed... Name: .config.gz Type: application/octet-stream Size: 51332 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/7c7845a2/attachment-0001.obj>
[Bug 97055] Black screens on A10-8780P (Carrizo) + R7 M260/M265 (Topaz) Combo
https://bugs.freedesktop.org/show_bug.cgi?id=97055 --- Comment #1 from Thomas J. Moore --- Created attachment 125268 --> https://bugs.freedesktop.org/attachment.cgi?id=125268&action=edit My latest Xorg.0.log Even though it's irrelevant to the fact that I couldn't even get console video, here's my Xorg.0.log. I suppose it may provide more detailed chip info than the kernel log. Also, I should mention that I diffed dmesg, Xorg.0.log, and xrandr outputs with and without video, and found no differences outside of time stamps (and of course the chosen crtc in xrandr when using that technique to get it working, but nothing is printed to kernel or X logs during this procedure). -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/89ce33cd/attachment.html>
[Bug 97055] Black screens on A10-8780P (Carrizo) + R7 M260/M265 (Topaz) Combo
https://bugs.freedesktop.org/show_bug.cgi?id=97055 Bug ID: 97055 Summary: Black screens on A10-8780P (Carrizo) + R7 M260/M265 (Topaz) Combo Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/AMDgpu Assignee: dri-devel at lists.freedesktop.org Reporter: darktjm at gmail.com Created attachment 125267 --> https://bugs.freedesktop.org/attachment.cgi?id=125267&action=edit dmesg from my latest boot (with some wifi messages at end deleted for privacy) I have an HP Pavilion 17-g133cl with A10 Carrizo+Topaz. I struggled for hours/days to get this to actually display anything at all using the amdgpu driver. In the mean time, efifb works perfectly every time (except of course no 3d, no X resolution switching, no brightness control, and slow enough that video playing is also impossible). Since it seemed like there were just issues powering up the display controller correctly, I decided at first to add my notes to https://bugzilla.kernel.org/show_bug.cgi?id=117591 but my symptoms (and cures) are, indeed, different. After much blind playing with my system (I have no way to ssh in, and the keyboard is flaky as well, so that was a lot of fun), I made the following observations: - kernel power management options appeared to have no effect - sometimes (very rarely), it just starts working, regardless - once it starts working for more than 1 minute, it stays working - often, it starts partially working, by giving me a flickering display - often, it starts working with a stable display, only to start flickering again after a few seconds (very rarely even going completely black gain) - my first way of fixing it is fairly reliable, but almost always requires at least one blind reboot before it starts giving my a display: xrandr --output eDP --crtc 1 (added to my .xinitrc) - if, when it finally comes up, it is flickering, it can be cured by toggling the crtc between 0 and 1 often enough until it remains stable for at least a minute. - if crtc 1 is enabled when X is killed, the machine goes blank and hangs hard; switching consoles while X is up works, though (although the consoles remain black). - changing the crtc to 1 in X does nothing for the console; only X displays anything. I have not tried to write a libdrm program to make the console switch to crtc 1, nor have I managed to trace where the crtc list comes from, or how to force it in the amdgpu driver itself. - if, instead of playing with the crtc, I play with power management again, I seem to be able to get it working by booting once with power management enabled, then rebooting with it disabled, and then it works (video in console as well as X, and no crtc switching necessary). However, that may just have been how it decides to work today, and tomorrow it will no longer work. I get identical behavior with kernels 4.6.2, 4.6.3, 4.6.4, 4.7-rc4 (which I decided to try given the supposed major amdgpu overhaul), 4.4.15 (which I decided to try given that the poster of the kernel.org bug was using Ubuntu's 4.4 kernel) (all on Gentoo; with the exception of 4.7-rc4, this is with Gentoo's fbdecor patches, but I obviously have that disabled while working through this problem). Overall, this is very weird and frustrating. I've had power management issues with previous Radeon laptops (all of them), but the gpu pm issue usually manifested as hard locks while playing games with power management enabled, not this crap. I have a feeling that anything that gets it to work only gets it to work due to random chance, and it's just that I'm beating at it often enough that I finally hit the jackpot at some point, and it keeps working correctly until I power cycle for an extended period again. I also get the feeling that I must be a major masochist to keep using ATI/AMD hardware, given that in 15+ years of using it I've never had an experience better than "meh, mostly works". If I weren't dead broke, I'd have chucked this machine over a freeway overpass and bought something else. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/279b66e5/attachment.html>
[Bug 91880] Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing
https://bugs.freedesktop.org/show_bug.cgi?id=91880 pc.jago1337 at gmail.com changed: What|Removed |Added Severity|minor |major Priority|medium |high --- Comment #114 from pc.jago1337 at gmail.com --- This bug really should be marked as MAJOR, seeing as how it literally runs the same as or worse than the R9 270X, which is something like $200 cheaper. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/2641c496/attachment.html>
[Bug 97038] OpenArena couple times slower using llvm 3.9
https://bugs.freedesktop.org/show_bug.cgi?id=97038 --- Comment #3 from smoki --- BTW not all but many apps runs in slowmo mode with llvm 3.9, not just ioquake3 based games. Should i start llvm bisect or not i dunno, as 3.9 enable GL 4.3 instead of 4.1 with llvm 3.8, i guess it might be mesa just set up something wrong too :) I might start banning some of those new extensions to found offender or so. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/0df4a3ed/attachment.html>
[Bug 97029] cik_sdma_copy_texture broken on Carrizo (mesa 12)
https://bugs.freedesktop.org/show_bug.cgi?id=97029 --- Comment #4 from Thomas J. Moore --- Created attachment 125266 --> https://bugs.freedesktop.org/attachment.cgi?id=125266&action=edit xwud results Sorry for the poor quality, late posting, and the reflections in the image. This is what the xwud output looks like. Notice the perfectly fine rxvt on the left (except for the blue crap in it; that was caused by xwud). The window in the middle is where xwud is supposed to put its output. Instead, it lays wide stripes to its right (far enough to reach around back to the left). Looks a lot like the stride and offset are wrong, but it also corrupts pixels in the top button bar. Also, I wanted to make it clear that this affects xv, ImageMagick-display, xpdf, and many other apps, not just some ancient screen capture program. The only thing keeping this from being a "major" issue is that it's easy to cure. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/f283dd19/attachment-0001.html>
[Bug 97038] OpenArena couple times slower using llvm 3.9
https://bugs.freedesktop.org/show_bug.cgi?id=97038 --- Comment #2 from smoki --- It is major PITA to do that on this low power APU... but if someone can't reproduce it or figure it out without bisecting i might do that i have time. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/b6e5820d/attachment.html>
[Bug 97039] The Talos Principle and Serious Sam 3 GPU faults
https://bugs.freedesktop.org/show_bug.cgi?id=97039 --- Comment #2 from smoki --- Test is on Kabini APU (i have Bonaire and Kaveri so i might test that too), but someone on irc already mentioned it happens with amdgpu on Bonaire... so yup if it does not happen with Tonga it might be CIK related. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/7683f762/attachment.html>
[Bug 97003] [d3dadapter+radeonsi] Dragon's Dogma: video memory leak with precompiled shaders
https://bugs.freedesktop.org/show_bug.cgi?id=97003 --- Comment #7 from Roland Scheidegger --- 0x36 looks like a segment override (ss segment) prefix (0x89 would be a mov), so nothing new. This looks like a valgrind bug to me: https://bugs.kde.org/show_bug.cgi?id=344139 which seems old, in particular no updates since over a year (and specifically mentions wine is using such segment override prefixes). -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160723/2b9e7af5/attachment.html>
