http://permalink.gmane.org/gmane.comp.video.dri.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.video.dri.devel/85310 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=44772 Harald Judt &lt;h.judt&lt; at &gt;gmx.at&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #10 from Harald Judt &lt;h.judt&lt; at &gt;gmx.at&gt; --- Solved by setting /sys/power/pm_async to 0. </pre> bugzilla-daemon< at >freedesktop.org 2013-05-26T05:35:24 http://permalink.gmane.org/gmane.comp.video.dri.devel/85309 <pre>Thanks, Anisse, but Dave's answer was wrong anyway. Using a different user-space-driver wouldn't have magically fixed the bug in the kernel KMS driver part. Eventually something newer will pop up in Debian SID and/or Debian Backports. I'll then pick it. As the performance of the device doesn't bother me, I see no need. The more I stay at what Debian provides, the less I have to maintain by myself :-) </pre> Holger Schurig 2013-05-24T15:01:41 http://permalink.gmane.org/gmane.comp.video.dri.devel/85308 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64983 --- Comment #3 from Knut Andre Tidemann &lt;knut.tidemann&lt; at &gt;gmail.com&gt; --- Created attachment 79791 --&gt; https://bugs.freedesktop.org/attachment.cgi?id=79791&amp;action=edit X3 correct rendering </pre> bugzilla-daemon< at >freedesktop.org 2013-05-25T16:11:10 http://permalink.gmane.org/gmane.comp.video.dri.devel/85307 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64983 --- Comment #2 from Knut Andre Tidemann &lt;knut.tidemann&lt; at &gt;gmail.com&gt; --- Created attachment 79790 --&gt; https://bugs.freedesktop.org/attachment.cgi?id=79790&amp;action=edit X3 corruption 3 </pre> bugzilla-daemon< at >freedesktop.org 2013-05-25T16:10:47 http://permalink.gmane.org/gmane.comp.video.dri.devel/85306 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64983 --- Comment #1 from Knut Andre Tidemann &lt;knut.tidemann&lt; at &gt;gmail.com&gt; --- Created attachment 79789 --&gt; https://bugs.freedesktop.org/attachment.cgi?id=79789&amp;action=edit X3 corruption 2 </pre> bugzilla-daemon< at >freedesktop.org 2013-05-25T16:10:26 http://permalink.gmane.org/gmane.comp.video.dri.devel/85305 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64983 Priority: medium Bug ID: 64983 Assignee: dri-devel&lt; at &gt;lists.freedesktop.org Summary: X3 Terran Conflict displays strange colors. Severity: normal Classification: Unclassified OS: Linux (All) Reporter: knut.tidemann&lt; at &gt;gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 79788 --&gt; https://bugs.freedesktop.org/attachment.cgi?id=79788&amp;action=edit X3 corruption 1 I'm running mesa 9.2 from git (fd9fe4470be0437c18cbd6d2bc8e568378f88200) and when starting X3: Terran Conflict, I see strange colors on the menu screen. This can also be seen in the game. It also seems that the colors change for each time the game is started. I've attached 4 pictures, the first three shows the incorrect colors in three different variations, and the last one shows the correct rendering (take</pre> bugzilla-daemon< at >freedesktop.org 2013-05-25T16:09:45 http://permalink.gmane.org/gmane.comp.video.dri.devel/85304 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64801 --- Comment #10 from Philip Prindeville &lt;philipp&lt; at &gt;redfish-solutions.com&gt; --- May 24 19:42:29 localhost kernel: [ 3836.454658] BUG: soft lockup - CPU#3 stuck for 22s! [Xorg:2347] May 24 19:42:29 localhost kernel: [ 3836.454662] Modules linked in: fuse bnep bluetooth rfkill hwmon_vid ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter xt_conntrack nf_conntrack ip6_tables snd_hda_codec_hdmi sp5100_tco i2c_piix4 snd_hda_codec_via snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer snd perle_serial(OF) r8169 acpi_cpufreq mperf soundcore kvm_amd kvm edac_core edac_mce_amd k10temp mii nfsd auth_rpcgss microcode serio_raw asus_atk0110 nfs_acl lockd uinput sunrpc usb_storage radeon i2c_algo_bit drm_kms_helper ttm ata_generic pata_acpi drm pata_atiixp i2c_core 3w_9xxx May 24 19:42:29 localhost kernel: [ 3836.454716] CPU 3 May 24 19:42:29 </pre> bugzilla-daemon< at >freedesktop.org 2013-05-25T01:43:10 http://permalink.gmane.org/gmane.comp.video.dri.devel/85303 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64801 --- Comment #9 from Philip Prindeville &lt;philipp&lt; at &gt;redfish-solutions.com&gt; --- And now I'm seeing: May 24 19:24:29 localhost kernel: [ 2756.377025] BUG: soft lockup - CPU#3 stuck for 23s! [Xorg:2347] May 24 19:24:29 localhost kernel: [ 2756.377028] Modules linked in: fuse bnep bluetooth rfkill hwmon_vid ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter xt_conntrack nf_conntrack ip6_tables snd_hda_codec_hdmi sp5100_tco i2c_piix4 snd_hda_codec_via snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer snd perle_serial(OF) r8169 acpi_cpufreq mperf soundcore kvm_amd kvm edac_core edac_mce_amd k10temp mii nfsd auth_rpcgss microcode serio_raw asus_atk0110 nfs_acl lockd uinput sunrpc usb_storage radeon i2c_algo_bit drm_kms_helper ttm ata_generic pata_acpi drm pata_atiixp i2c_core 3w_9xxx May 24 19:24:29 localhost kernel: [ 2756.377082] CPU</pre> bugzilla-daemon< at >freedesktop.org 2013-05-25T01:27:52 http://permalink.gmane.org/gmane.comp.video.dri.devel/85302 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=63935 --- Comment #45 from SMF &lt;smf.linux&lt; at &gt;ntlworld.com&gt; --- On 05/24/13 13:01, bugzilla-daemon&lt; at &gt;freedesktop.org wrote: I got exactly same issue on [AMD/ATI] RV710 [Radeon HD 4350/4550] with RV710_uvd.bin with 3.10-rc2 kernel. Will also test again with next rc. </pre> bugzilla-daemon< at >freedesktop.org 2013-05-25T00:01:22 http://permalink.gmane.org/gmane.comp.video.dri.devel/85300 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64201 --- Comment #28 from Olivier Langlois &lt;olivier&lt; at &gt;olivierlanglois.net&gt; --- if this can help: llvm::Linker::SrcM is NULL (gdb) where #0 _M_data (this=0x90) at /usr/include/c++/4.8.0/bits/basic_string.h:293 #1 _M_rep (this=0x90) at /usr/include/c++/4.8.0/bits/basic_string.h:301 #2 size (this=0x90) at /usr/include/c++/4.8.0/bits/basic_string.h:716 #3 empty (this=0x90) at /usr/include/c++/4.8.0/bits/basic_string.h:812 #4 run (this=0x7fffe1bd7e30) at LinkModules.cpp:1152 #5 llvm::Linker::linkInModule (this=this&lt; at &gt;entry=0x7fffe1bd8190, Src=Src&lt; at &gt;entry=0x0, Mode=Mode&lt; at &gt;entry=0, ErrorMsg=ErrorMsg&lt; at &gt;entry=0x7fffe1bd83c0) at LinkModules.cpp:1302 #6 0x00007f74fe1870ef in llvm::Linker::LinkModules (Dest=&lt;optimized out&gt;, Src=0x0, Mode=0, ErrorMsg=0x7fffe1bd83c0) at LinkModules.cpp:1322 #7 0x00007f74ff96eecc in clover::compile_program_llvm(clover::compat::string const&amp;, pipe_shader_ir, clover::compat::string const&amp;, clover::compat::string const&amp;) () from /usr/li</pre> bugzilla-daemon< at >freedesktop.org 2013-05-24T18:50:09 http://permalink.gmane.org/gmane.comp.video.dri.devel/85299 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=61533 --- Comment #10 from Anton Petrov &lt;m2d&lt; at &gt;sibnet.ru&gt; --- Looks like what my problem disappeared after some of the latest commits (glsl related?). Two days ago i disabled HyperZ via env vars and lockups in minecraft gone. But today i updated from git and enabled HyperZ to see if that happens again, but everything is good. If it necessary i can try to figure out what commit fixed this. Still have some quite rare hangups in some cases but it's not critical as they quickly gone. Strange. Thank you anyway. </pre> bugzilla-daemon< at >freedesktop.org 2013-05-24T18:01:32 http://permalink.gmane.org/gmane.comp.video.dri.devel/85298 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64201 --- Comment #27 from Olivier Langlois &lt;olivier&lt; at &gt;olivierlanglois.net&gt; --- (In reply to comment #26) Ok. I'm a bit surprise given that this GPU is in the R600 row at: http://www.x.org/wiki/RadeonFeature#Decoder_ring_for_engineering_vs_marketing_names I'll stop my effort to investigate this problem then. Thank you for your prompt reply. </pre> bugzilla-daemon< at >freedesktop.org 2013-05-24T17:50:35 http://permalink.gmane.org/gmane.comp.video.dri.devel/85297 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64801 --- Comment #8 from Philip Prindeville &lt;philipp&lt; at &gt;redfish-solutions.com&gt; --- mesa-libgbm-9.1-3.fc18.x86_64 mesa-dri-drivers-9.1-3.fc18.x86_64 mesa-libGLU-9.0.0-1.fc18.x86_64 mesa-libGL-devel-9.1-3.fc18.x86_64 mesa-dri-filesystem-9.1-3.fc18.x86_64 mesa-libEGL-devel-9.1-3.fc18.x86_64 mesa-libxatracker-9.1-3.fc18.x86_64 mesa-libGL-9.1-3.fc18.x86_64 mesa-libEGL-9.1-3.fc18.x86_64 mesa-libglapi-9.1-3.fc18.x86_64 </pre> bugzilla-daemon< at >freedesktop.org 2013-05-24T17:13:17 http://permalink.gmane.org/gmane.comp.video.dri.devel/85296 <pre>latest git tree gives : CHK kernel/config_data.h CC [M] drivers/gpu/drm/qxl/qxl_fb.o drivers/gpu/drm/qxl/qxl_fb.c:162:15: error: variable ‘qxl_defio’ has initializer but incomplete type drivers/gpu/drm/qxl/qxl_fb.c:163:2: error: unknown field ‘delay’ specified in initializer drivers/gpu/drm/qxl/qxl_fb.c:163:2: warning: excess elements in struct initializer [enabled by default] drivers/gpu/drm/qxl/qxl_fb.c:163:2: warning: (near initialization for ‘qxl_defio’) [enabled by default] drivers/gpu/drm/qxl/qxl_fb.c:164:2: error: unknown field ‘deferred_io’ specified in initializer drivers/gpu/drm/qxl/qxl_fb.c:164:2: warning: excess elements in struct initializer [enabled by default] drivers/gpu/drm/qxl/qxl_fb.c:164:2: warning: (near initialization for ‘qxl_defio’) [enabled by default] drivers/gpu/drm/qxl/qxl_fb.c: In function ‘qxlfb_create’: drivers/gpu/drm/qxl/qxl_fb.c:456:6: error: ‘struct fb_info’ has no member named ‘fbdefio’ make[4]: *** [drivers/gpu/drm/qxl/qxl_fb.o] E</pre> Toralf Förster 2013-05-24T17:13:02 http://permalink.gmane.org/gmane.comp.video.dri.devel/85295 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64471 --- Comment #5 from Zoltán Böszörményi &lt;zboszor&lt; at &gt;pr.hu&gt; --- The lockup also happens with mesa commit 0b5b3f8816f9cb5a2b2259176b4c7dd9e4d31233 and llvm-3.3, whatever commit it is at in current Fedora 19 beta. </pre> bugzilla-daemon< at >freedesktop.org 2013-05-24T17:08:38 http://permalink.gmane.org/gmane.comp.video.dri.devel/85294 <pre> I was mainly thinking about the current drivers that already depend on planes for scanout. We don't want to go blindly disable all planes in the core since the driver is the one that knows which plane it needs for the crtc scanout duties. Sure, it's a hack. Good point. So what about set_par/pan_display? Do you want the fbdev restore thingy to permanently disable the planes/cursors, as in update our s/w state to indicate that they're disabled and hence won't get restored unless someone explicitly re-enables them? Because that's not what the current code does. </pre> Ville Syrjälä 2013-05-24T17:06:48 http://permalink.gmane.org/gmane.comp.video.dri.devel/85293 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64201 --- Comment #26 from Tom Stellard &lt;tstellar&lt; at &gt;gmail.com&gt; --- Sorry, OpenCL is not supported for RS780. </pre> bugzilla-daemon< at >freedesktop.org 2013-05-24T16:08:26 http://permalink.gmane.org/gmane.comp.video.dri.devel/85292 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=64201 Olivier Langlois &lt;olivier&lt; at &gt;olivierlanglois.net&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |olivier&lt; at &gt;olivierlanglois.net --- Comment #25 from Olivier Langlois &lt;olivier&lt; at &gt;olivierlanglois.net&gt; --- Hi, I have a segfault when running bfgminer. I have compiled llvm,libclc and mesa yesterday from git/svn trunk. The core seems to happen when llvm compiles the cl program. So the crash happens before anything gets executed on the GPU. Maybe llvm is compiling differently depending on the target. I am currently rebuilding debug build of llvm to have more info but in the meantime, just in case that you would recognize something you've seen often: Program terminated with signal 11, Segmentation fault. #0 0x00007f090591a5e5 in llvm::Linker::linkInModule(llvm::Module*, unsigned int, std::string*) () from /usr/lib/llvm/libLLVM</pre> bugzilla-daemon< at >freedesktop.org 2013-05-24T16:00:51 http://permalink.gmane.org/gmane.comp.video.dri.devel/85291 <pre>On Fri, May 24, 2013 at 11:59 AM, Ville Syrjälä &lt;ville.syrjala&lt; at &gt;linux.intel.com&gt; wrote: I guess the aim is to use the plane scaler and blast the fbcon output over whatever resolution we're currently displaying for e.g. an oops? Even then I don't see how this is any different from Wayland blasting a fullscreen app all over the screen. And if our drm core -&gt; driver interface isn't good enough for fbcon to do that, Wayland won't ever get it right. So all I'm saying is that proper fbcon safe/restore looks like a neat in-kernel test-bed to check interfaces. And we should go with that approach instead of rolling driver hacks. And splattering is_fbcon_crtc checks all over _is_ imo a great hack. Atm kms client state management is purely driven by vt switching, and we don't have any guarantees at all that state survives a vt switch. Hence both X and Wayland already fully restore kms state. So in the current model we don't need any state safe/restore in the kernel. Also I'm not sure whether doing that state safe</pre> Daniel Vetter 2013-05-24T15:14:40 http://permalink.gmane.org/gmane.comp.video.dri.devel/85290 <pre>On Mon, 13 May 2013 15:02:46 +0200, Holger Schurig &lt;holgerschurig&lt; at &gt;gmail.com&gt; wrote : The wheezy driver is too old, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683526 So no wonder it doesn't work. You can try applying the patches manually or just compiling a more recent version of xf86-video-modesetting. Make yourself known on this debian bug if it fixes it for you. Regards, Anisse </pre> Anisse Astier 2013-05-24T14:51:35 http://permalink.gmane.org/gmane.comp.video.dri.devel/85289 <pre>https://bugs.freedesktop.org/show_bug.cgi?id=27211 --- Comment #17 from Mauro Molinari &lt;mauromol&lt; at &gt;tiscali.it&gt; --- Hi Marcin, I have a Creative Labs Graphics Blaster Riva TNT and I encountered this problem on both Debian Squeeze (with 2.6.32 kernel) and Linux Mint 12 LXDE (with 3.0 kernel). Symptom: during boot, the screen goes blank (some garbage shown) and the boot process does not terminate. dmesg shows an endless list of "PGRAPH_NOTIFY - nSource: PATCH_EXCEPTION, nStatus: INVALID_STATE PROTECTION_FAULT" errors. To fix the problem I was using the "nomodeset" kernel booting parameter, then I found this bug report and I ended up with "nouveau.noaccel=1" which at least gives me a high definition console. As far as I understand it correctly, now the problem is solved (i.e.: no need for nouveau.noaccel=1 anymore), but which kernel version does carry the fixed nouveau driver? </pre> bugzilla-daemon< at >freedesktop.org 2013-05-24T14:03:59 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.video.dri.devel