Re: [Dri-devel] Deadlock with radeon DRI

2003-10-11 Thread Mike A. Harris
On Fri, 10 Oct 2003, Keith Whitwell wrote: Date: Fri, 10 Oct 2003 21:55:57 +0100 From: Keith Whitwell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: DRI Devel [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii; format=flowed Subject: Re: [Dri-devel] Deadlock

Re: [Dri-devel] Deadlock with radeon DRI

2003-10-10 Thread John Dennis
The locking problem is solved, my original analysis was incorrect. The problem was that DRM_CAS was not correctly implemented on IA64. Thus this was an IA64 issue only, this is consistent with others who showed up in a google search describing the problem, all were on IA64. I have filed an

Re: [Dri-devel] Deadlock with radeon DRI

2003-10-10 Thread Keith Whitwell
John Dennis wrote: The locking problem is solved, my original analysis was incorrect. The problem was that DRM_CAS was not correctly implemented on IA64. Thus this was an IA64 issue only, this is consistent with others who showed up in a google search describing the problem, all were on IA64. I

Re: [Dri-devel] Deadlock with radeon DRI

2003-10-02 Thread Keith Whitwell
John Dennis wrote: [Note: this is cross posted between dri-devel and [EMAIL PROTECTED] ] I'm trying to debug a hung X server problem with DRI using the radeon driver. Sources are XFree86 4.3.0. This happens to be on ia64, but at the moment I don't see anything architecture specific about the

Re: [Dri-devel] Deadlock with radeon DRI

2003-10-02 Thread Keith Whitwell
Keith Whitwell wrote: John Dennis wrote: [Note: this is cross posted between dri-devel and [EMAIL PROTECTED] ] I'm trying to debug a hung X server problem with DRI using the radeon driver. Sources are XFree86 4.3.0. This happens to be on ia64, but at the moment I don't see anything architecture

Re: [Dri-devel] Deadlock with radeon DRI

2003-10-02 Thread Ian Romanick
Keith Whitwell wrote: I haven't deeply investigated this but two solutions spring to mind: - Hack: Move the call to RADEONAdjustFrame() during initialization to before the lock is grabbed. - Better: Replace the call to RADEONAdjustFrame() during initialization with something like: