https://bugs.freedesktop.org/show_bug.cgi?id=66515
--- Comment #19 from Mauro Carvalho Chehab <[email protected]> --- (In reply to comment #18) > (In reply to comment #17) > > Although --enable-glx-tls is not explicitly specified. But it detect whether > > the tls is supported, and if it's supported, it will enable glx-tls which is > > the same way what xorg's autoconf does. > > Then glamor's configure --help output should reflect that. Yep. Anyway, I double-checked by compiling it on mock (mock gets the standard Fedora packages, instead of my modified ones). From it, TLS seems to be enabled: ... checking for XORG... yes checking for DRI2... yes checking whether to include GLAMOR_GLES2 support... no checking whether to enable DEBUG... no checking for GL... yes checking for LIBDRM... yes checking for EGL... yes checking for GBM... yes checking for thread local storage (TLS) support... __thread checking for tls_model attribute support... yes checking that generated files are newer than configure... done > > > > And tls is almost always supported, so that make glamor require a mesa with > > --enable-glx-tls specified explicitly. > > But if I understand correctly, Mauro is saying that this problem happens > when Mesa is built with --enable-glx-tls, but not without... Yes. When mesa is compiled with --enable-glx-tls, either mesa or glamor seem to sendinvalid or incomplete commands to Cape Verde GPU on some situations (combo boxes), causing it to wait forever to complete and hanging Xorg. The GPU itself doesn't hang, as it is still possible to press CTRL-ALT-F2 to move to a console terminal. So, it seems that the Kernel radeon driver remains working properly. -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
