Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Apr 2009 18:44:58 +0200
From:      deeptech71@gmail.com
To:        freebsd-current@freebsd.org
Subject:   Re: diagnosing freezes (DRI?)
Message-ID:  <49EA038A.7080603@gmail.com>
In-Reply-To: <1240002714.24514.13.camel@balrog.2hip.net>
References:  <49E6ACEE.6080301@gmail.com>	 <200904161116.58094.jhb@freebsd.org>	 <1239913234.1991.1.camel@balrog.2hip.net> <49E7FED0.9090708@gmail.com> <1240002714.24514.13.camel@balrog.2hip.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Robert Noland wrote:
> On Fri, 2009-04-17 at 06:00 +0200, deeptech71@gmail.com wrote:
>> Robert Noland wrote:
>>> On Thu, 2009-04-16 at 11:16 -0400, John Baldwin wrote:
>>>> The drm code is doing a copyin() while holding a mutex (which is not allowed).
>>> Ok, the quick and dirty fix for this is
>>> http://people.freebsd.org/~rnoland/drm_radeon_state-copyin-fix.patch
>>>
>>> I think there may be other places of concern though and a more proper
>>> fix is needed.
>> I still get the same lockup :(
> 
> Ok, try this one... It should address all of the copyin/copyout paths in
> radeon.  the r300_cmdbuf.c bits worry me a little, but I'm running this
> way now....
> 
> http://people.freebsd.org/~rnoland/drm_radeon-copyin-fix-try2.patch

OK, I can't seem to reproduce the crash with this patch. Thanks.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49EA038A.7080603>