Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-03-24 Thread DRC
With the help of nVidia, I was able to get to the bottom of what's going on with WINE 1.3.11+. In fact, it has nothing to do with WINE. Any application that attempts to call glXSwapIntervalSGI() with a Pbuffer current will cause nVidia GLX to trip a BadWindow error. This has been the case at lea

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-03-03 Thread DRC
On 3/3/11 11:21 AM, Nathan Kidd wrote: > Another approach to deal with this could be to remove > GLX_SGI_swap_control from the extension list. At least this way > (well-behaved) apps would *know* they can't control the update speed. > (Although in wine's case it will simply warn and carry on, so t

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-03-03 Thread Nathan Kidd
On 11-03-02 05:14 PM, DRC wrote: > Bingo. > > Apparently nVidia is trying to outsmart us yet again and is somehow > making a determination in the underlying GLX library that it needs to > send glXSwapIntervalSGI() over the wire rather than to the display on > which the GLX context has been establis

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-03-03 Thread calvin . morrow
From: "DRC" To: "calvin morrow" Cc: "Nathan Kidd" , "VirtualGL Users" Sent: Wednesday, March 2, 2011 3:14:56 PM Subject: Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10 Bingo. Apparently nVidia is trying

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-03-02 Thread DRC
Error of failed request: BadWindow (invalid Window parameter) > Major opcode of failed request: 135 (GLX) > Minor opcode of failed request: 16 (X_GLXVendorPrivate) > Resource id in failed request: 0x446 > Serial number of failed request: 0 > Current serial number in out

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-28 Thread DRC
On 2/28/11 6:20 PM, Nathan Kidd wrote: > On 11-02-28 07:04 PM, DRC wrote: >> I'm not following how you ascertained that the issue was between WINE >> and the 3D X server. > > Sorry, I didn't mention that part. I ran against an in-house X server > with tracing enabled and examined the trace. No GL

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-28 Thread Nathan Kidd
On 11-02-28 07:04 PM, DRC wrote: > I'm not following how you ascertained that the issue was between WINE > and the 3D X server. Sorry, I didn't mention that part. I ran against an in-house X server with tracing enabled and examined the trace. No GLX, and more importantly, no X errors returned at

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-28 Thread DRC
I'm not following how you ascertained that the issue was between WINE and the 3D X server. On 2/28/11 5:11 PM, Nathan Kidd wrote: > I was finally able to reproduce. > > a) I had to update my NVIDIA driver from a pretty old 185 to 260. > b) Used Wine 1.3.14 (from ubuntu-wine/ppa karmic) and fr-04

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-28 Thread Nathan Kidd
I was finally able to reproduce. a) I had to update my NVIDIA driver from a pretty old 185 to 260. b) Used Wine 1.3.14 (from ubuntu-wine/ppa karmic) and fr-041_debris.exe c) The problem is not between wine and the 2D xserver, but wine and the 3D Xserver. Wine must be doing a GetCurrentDisplay().

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-27 Thread DRC
nt: Friday, February 25, 2011 4:24:39 PM > Subject: Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer > than 1.3.10 > > On 11-02-25 06:19 PM, DRC wrote: > >> If we're getting a BadWindow error it had to be issued by the 2D X > >> server. Therefore

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-27 Thread calvin . morrow
e, however I might need more guidance on forcing an indirect context. Calvin - Original Message - From: "Nathan Kidd" To: "VirtualGL Users" Sent: Friday, February 25, 2011 4:24:39 PM Subject: Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer t

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-25 Thread DRC
See Calvin's previous post. There's a link to a D3D app buried in there that repros the problem. I'm using the 1.3.13 WINE RPMs from here: http://packages.sw.be/wine/ On 2/25/11 5:24 PM, Nathan Kidd wrote: > What was the final recipe to reproduce? Specific wine version, specific app?

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-25 Thread Nathan Kidd
On 11-02-25 06:19 PM, DRC wrote: >> If we're getting a BadWindow error it had to be issued by the 2D X >> server. Therefore, force an indirect context and grab a wireshark >> trace. The actual VendorPrivate call has to be there. Once we know >> which vop it is then the grepping will be easier. >

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-25 Thread DRC
> If we're getting a BadWindow error it had to be issued by the 2D X > server. Therefore, force an indirect context and grab a wireshark > trace. The actual VendorPrivate call has to be there. Once we know > which vop it is then the grepping will be easier. If you or someone else has the tim

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-25 Thread Nathan Kidd
On 11-02-25 05:52 PM, DRC wrote: > As far as what to call the X servers, I've taken to using the terms "2D > X server" and "3D X server" in the VGL documentation. > > I was able to reproduce the failure using my systems. I tried setting > VGL_X11TRAP=1 to force X11 to call xhandler() in faker.cpp,

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-25 Thread DRC
erial number in output stream: 99 > > Calvin > > > > ----- Original Message - > From: "DRC" > To: virtualgl-users@lists.sourceforge.net > Sent: Thursday, February 24, 2011 12:03:22 PM > Subject: Re: [VirtualGL-Users] VirtualGL Linux wine crash in versio

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-24 Thread calvin . morrow
umber of failed request: 0 Current serial number in output stream: 99 Calvin - Original Message - From: "DRC" To: virtualgl-users@lists.sourceforge.net Sent: Thursday, February 24, 2011 12:03:22 PM Subject: Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer t

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-24 Thread calvin . morrow
er way, the solution is figure out which function call it is and then for VGL to hook it. -Nathan > - Original Message - > From: "Nathan Kidd" > To: "VirtualGL Users" > Sent: Thursday, February 24, 2011 8:50:48 AM > Subject: Re: [VirtualGL-Use

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-24 Thread DRC
I can't reproduce the failure with WINE 1.3.13. Can you give more specific information-- what graphics hardware you are using, the specific driver version, what O/S, etc.? After looking at the WINE source, the only scenario I can come up with is that it's trying to use glXBindTexImageATI(), which

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-24 Thread Nathan Kidd
On 11-02-24 01:24 PM, Nathan Kidd wrote: > VGL doesn't hook > any vendor private calls, so ... Correction: VGL doesn't appear to hook this vendor private function. -- Free Software Download: Index, Search & Analyze Logs

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-24 Thread Nathan Kidd
VGL to hook it. -Nathan > - Original Message - > From: "Nathan Kidd" > To: "VirtualGL Users" > Sent: Thursday, February 24, 2011 8:50:48 AM > Subject: Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions > newer than 1.3.10 > > On 11-02-24 10:32

Re: [VirtualGL-Users] VirtualGL Linux wine crash in versions newer than 1.3.10

2011-02-24 Thread Nathan Kidd
On 11-02-24 10:32 AM, calvin.mor...@comcast.net wrote: > Hello List, > > I'm finding that VirtualGL has been working well with most graphics > applications I've tried under Linux, and even with pretty decent > performance. > > I have been running several Windows applications using wine and > Virtua