Diagnosing first vs subsequent performance

2016-01-19 Thread Lloyd Brown
ide the GPU device section. I can verify via nvidia-smi, that the separate Xorg PIDs are attached to the correct GPUs. -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu Section "ServerLayout" Identifier "Layout0

Re: Diagnosing first vs subsequent performance

2016-01-19 Thread Lloyd Brown
to remove other config data that could be part of > the issue. Again, just guessing, and might be a quick and easy test. -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu ___ xorg@lists.

Re: Diagnosing first vs subsequent performance

2016-01-19 Thread Lloyd Brown
upgrade to the RHEL xorg-x11-server-Xorg RPM to v1.15.0-36. It did not have any effect; the same behavior occurred either way. Lloyd On 01/19/2016 12:05 PM, Ilya Anfimov wrote: > Good day. Could you provide glxinfo output, first and second run on > different displays? -- Lloyd Brown Sy

Re: Diagnosing first vs subsequent performance

2016-01-19 Thread Lloyd Brown
necessary, but it also means that nothing I eliminated was actually the problem. Lloyd On 01/19/2016 11:54 AM, Lloyd Brown wrote: > I will try, but honestly, I'm not certain if it will instantiate the > server or not. > > I was mostly following the recommendations from th

Re: Diagnosing first vs subsequent performance

2016-01-20 Thread Lloyd Brown
stance glxgears on the GPU? > > Cheers, > Thomas > ___ > xorg@lists.x.org: X.Org support > Archives: http://lists.freedesktop.org/archives/xorg > Info: http://lists.x.org/mailman/listinfo/xorg > Your subscription address: %(user_address)s -- Lloyd Brown Systems Administrator F

Re: Diagnosing first vs subsequent performance

2016-01-20 Thread Lloyd Brown
I don't see how else one Xorg display could have this kind of effect on another. Lloyd On 01/20/2016 12:49 PM, Lloyd Brown wrote: > It's true. A glxinfo first, is enough to get things working, so that's > a workaround. Not ideal, but something. > > As far as dmesg,

Re: Diagnosing first vs subsequent performance

2016-01-20 Thread Lloyd Brown
e GPU access whenever the one you touched last grabs the VT. > > You can work around this problem somewhat by using the -sharevts and > -novtswitch options to make the X servers be active simultaneously, but > please be aware that this configuration is not officially supported so > you mig

Re: Diagnosing first vs subsequent performance

2016-01-21 Thread Lloyd Brown
not a huge deal either way. Just a personal preference to have config files vs cli params. Thanks, Lloyd On 01/20/2016 04:57 PM, Lloyd Brown wrote: > Wow, Aaron. I should've known that you'd have the answer. Thanks, btw, > for answering my earlier, semi-related questions on

Major/Minor Opcodes of failed requests

2016-03-30 Thread Lloyd Brown
nt me in the right direction, that would be helpful. Thanks, -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/x

Re: Major/Minor Opcodes of failed requests

2016-03-30 Thread Lloyd Brown
enormously large > pixmaps. Of course there's many things that can cause this. Decoding the > opcode will help you debug it. > > > Regards > Ingo > > On 03/30/2016 06:03 PM, Lloyd Brown wrote: >> Can anyone help me understand where the error messages, especially the