search for: glxtest

https://bugs.freedesktop.org/show_bug.cgi?id=75279 --- Comment #3 from Benoit Jacob <bjacob at mozilla.com> --- Created attachment 94465 --> https://bugs.freedesktop.org/attachment.cgi?id=94465&action=edit Stand-alone version of the glxtest program Here you go. build like this: c++ glxtest.cpp -o glxtest -ldl -lX11 run like this: ./glxtest Example output: VENDOR Tungsten Graphics, Inc RENDERER Mesa DRI Intel(R) Sandybridge Mobile VERSION 3.0 Mesa 8.0.4 TFP TRUE -- You are receiving this mail because: You are...

https://bugs.freedesktop.org/show_bug.cgi?id=79823 Priority: medium Bug ID: 79823 Assignee: nouveau at lists.freedesktop.org Summary: Mozilla apps freeze on startup with nouveau-dri-10.2.1 libs on dual-screen Severity: normal Classification: Unclassified OS: Linux (All) Reporter: natrio at

https://bugs.freedesktop.org/show_bug.cgi?id=75279 --- Comment #9 from Frederic Bezies <fredbezies at gmail.com> --- glxtest output : [fred at fredo-arch ~]$ ./glxtest VENDOR nouveau RENDERER Gallium 0.4 on NVA8 VERSION 3.0 Mesa 10.0.3 TFP TRUE Not a single hang. Will try seeing on full mozilla code if there is still a hang or not. -- You are receiving this mail because: You are the assignee for the bug. -----------...

...eedesktop.org/show_bug.cgi?id=75279 --- Comment #32 from Benoit Jacob <bjacob at mozilla.com> --- ...note that the log attached by Frederic in comment 30 also has a stack to where this pointer was free'd --- we have a use-after-free bug here! This was obtained by Frederic by running the glxtest program attached in comment 2 here, in valgrind: valgrind --track-origins=yes ./glxtest I hope that Nouveau developers here can reproduce this easily! -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrub...

https://bugs.freedesktop.org/show_bug.cgi?id=75279 --- Comment #37 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #36) > Can you reproduce yourself by running the attached glxtest program in > valgrind? Oh, I'm sure (can't right now, will try tonight). But I doubt it's the source of the bug. The glxtest program doesn't appear to hang. Memory is unlikely to be reallocated _so_ quickly, that ->state would change. (Although more likely in a multithreaded...

...n't clear enough in comment 34, let me explain better :-) The Mozilla change that exposed this, https://bugzilla.mozilla.org/show_bug.cgi?id=860254, is exactly about having memory overwritten immediately on free(). So this is _exactly_ what is happening here :-) The reason why the stand-alone glxtest program doesn't hang is that it doesn't use Mozilla's modified memory allocator that overwrites memory on free(). If you ran it with this memory allocator, no doubt that it would hang there, as this loop would keep reading a wrong fence->status. So what you can hope to reproduce you...

https://bugs.freedesktop.org/show_bug.cgi?id=75279 --- Comment #2 from Emil Velikov <emil.l.velikov at gmail.com> --- If you can hack out the glxtest into a separate program that would ease all of use alot. Cheers -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20140220/52460d1c...

...m.mit.edu> --- (In reply to comment #4) > I have also asked the original reporter to share his glxinfo output and > details about his setup. You might want to CC yourself on the mozilla bug. Might be easier to get the original reporter onto this one... Can you confirm that the standalone glxtest causes the reported 1-minute stall as well? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20140221/a1523bff/attachment.html>

...changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fredbezies at gmail.com --- Comment #10 from Ilia Mirkin <imirkin at alum.mit.edu> --- Emil tried the glxtest program earlier and didn't get a hang either. So at least that's consistent. (I'm adding you to the CC list, hope that's OK, if not, feel free to remove yourself.) -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An...

https://bugs.freedesktop.org/show_bug.cgi?id=75279 --- Comment #11 from Frederic Bezies <fredbezies at gmail.com> --- (In reply to comment #10) > Emil tried the glxtest program earlier and didn't get a hang either. So at > least that's consistent. (I'm adding you to the CC list, hope that's OK, if > not, feel free to remove yourself.) I don't mind. I wanted to do so :) -- You are receiving this mail because: You are the assignee for th...

https://bugs.freedesktop.org/show_bug.cgi?id=75279 --- Comment #13 from Benoit Jacob <bjacob at mozilla.com> --- The work-around that works for us, and that we're considering landing, is to avoid calling XCloseDisplay and, in this case, just calling XSync to handle any pending errors in glxtest. Digging in the Gecko codebase, I found at least another instance where we avoid calling XCloseDisplay because it is "scary": http://hg.mozilla.org/mozilla-central/file/2d5d5fd03050/dom/plugins/ipc/PluginModuleChild.cpp#l569 At the moment I am wondering if we should stop calling XCloseD...

...000321f61c526 in FreeScreenConfigs.isra.3 () from /lib64/libGL.so.1 #8 0x000000321f61c5a5 in glx_display_free () from /lib64/libGL.so.1 #9 0x000000321f61c6a5 in __glXCloseDisplay () from /lib64/libGL.so.1 #10 0x0000003f3e21fd22 in XCloseDisplay () from /lib64/libX11.so.6 #11 0x00007f1e09933dcf in glxtest() () from /home/sstangl/bin/nightly/libxul.so #12 0x00007f1e09934b36 in fire_glxtest_process() () from /home/sstangl/bin/nightly/libxul.so #13 0x00007f1e0992e655 in XREMain::XRE_mainInit(bool*) () from /home/sstangl/bin/nightly/libxul.so #14 0x00007f1e09932886 in XREMain::XRE_main(int, char**...

...ug.cgi?id=75279 --- Comment #20 from Emil Velikov <emil.l.velikov at gmail.com> --- Hi Benoit IMHO the stack trace does not indicate where the problem occurs, just that there is one. - Are you guys using multi-threaded gl ? - Considering that the problem is not available with a standalone glxtest app, do you have a link to a FF build that one can test against ? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20140225/f64b46...

...-enabled and 2) viewing specific Web pages (e.g. using WebGL). But here we are talking about a startup hang occurring before this could kick into play. Frederic, can you say if you have any force-enabled prefs set in about:config? - Considering that the problem is not available with a standalone glxtest app, do you have a link to a FF build that one can test against ? Sure. You need a Nightly build, but not a current one since we have landed a work-around (avoiding to call XCloseDisplay here). This one, from Feb. 20, should reproduce: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014-0...

...like a NouVeau is triggered by Mozilla Firefox trunk code. I opened a bug on mozilla bugtracker, https://bugzilla.mozilla.org/show_bug.cgi?id=978439 Even if I find a "dirty workaround", valgrind logs are showing a NouVeau driver bug. I will attach both Mozilla Firefox valgrind log and glxtest one. But there is a common part : Invalid read of size 4 at 0x8DBA0BE: nouveau_fence_wait (nouveau_fence.c:205) by 0x8E4AFF4: nv50_screen_destroy (nv50_screen.c:293) by 0x8DAACDE: dri_destroy_screen_helper (dri_screen.c:378) by 0x8DAAD74: dri_destroy_screen (dri_screen.c:388)...

https://bugs.freedesktop.org/show_bug.cgi?id=75279 --- Comment #30 from Frederic Bezies <fredbezies at gmail.com> --- Created attachment 95188 --> https://bugs.freedesktop.org/attachment.cgi?id=95188&action=edit Valgrind log for glxtest Here is the valgrind log for Glx test -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20140305/69f7d385/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=75279 --- Comment #36 from Benoit Jacob <bjacob at mozilla.com> --- Can you reproduce yourself by running the attached glxtest program in valgrind? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20140305/6289d01c/attachment.html>

...OS: Linux (All) Reporter: sacanti.ernesto at gmail.com Hardware: x86 (IA32) Status: NEW Version: unspecified Component: Driver/nouveau Product: xorg Firefox 18.0.2 and Thunderbird 17.0.2 crashes randomly. Error Report:GLXtest process failed (exited with status 1): X error occurred in GLX probe, error_code=11, request_code=154, minor_code=3 lspci command: 02:00.0 VGA compatible controller: nVidia Corporation NVCrush11 [GeForce2 MX Integrated Graphics] (rev b1) (prog-if 00 [VGA controller]) Subsystem: nVidia Corporat...