From owner-freebsd-current@FreeBSD.ORG  Tue Dec 31 00:33:26 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id B44E1AE2
 for <freebsd-current@freebsd.org>; Tue, 31 Dec 2013 00:33:26 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 470001F8A
 for <freebsd-current@freebsd.org>; Tue, 31 Dec 2013 00:33:26 +0000 (UTC)
Received: from [157.181.98.186] ([157.181.98.186]) by mail.gmx.com (mrgmx003)
 with ESMTPSA (Nemesis) id 0Mg42v-1Vm1gR2wQn-00NPOF for
 <freebsd-current@freebsd.org>; Tue, 31 Dec 2013 01:33:18 +0100
Message-ID: <52C210A4.8080008@gmx.com>
Date: Tue, 31 Dec 2013 01:32:36 +0100
From: dt71@gmx.com
User-Agent: Mozilla/5.0 (X11; FreeBSD i386;
 rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20
MIME-Version: 1.0
To: Adrian Chadd <adrian@freebsd.org>
Subject: Re: new Xorg (KMS, etc.) for Radeon 9600
References: <527F95BE.7080908@gmx.com>	<Pine.GSO.4.64.1311101135590.9459@sea.ntplx.net>	<527FC05D.8080703@gmx.com>	<5283E123.5000305@FreeBSD.org>	<20131114113846.4dcb2037@kalimero.tijl.coosemans.org>	<52858067.2060200@gmx.com>	<52AEAD7A.1040205@gmx.com>	<52B0C004.9010702@FreeBSD.org>	<52B14384.5060102@gmx.com>
 <CAJ-VmokrhMB5MGhPKFw70rFbSCy0EtD0ueaUJQs5OhYR0j=wbg@mail.gmail.com>
In-Reply-To: <CAJ-VmokrhMB5MGhPKFw70rFbSCy0EtD0ueaUJQs5OhYR0j=wbg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Z8flkab/KlOm5dOB21+RvIbpobBJ+59JXrpgtzDOZwYWqcdxwUQ
 Kp6sfI20OxwseACgESI9NF7AQVxy13/Dn+echp4FRKtVh3pooaQ8DONdy9RhyX1pMsbg8Cz
 5qvJuBjyhsPgEA56ou0czlHEqbUSTs2UzBWmJQnG40MzRvDwyto7PUnVwAcerOeG3lo4TV+
 UB5H11eaqj+SEzR+ywdow==
Cc: freebsd-current <freebsd-current@freebsd.org>,
 =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= <dumbbell@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Dec 2013 00:33:26 -0000

Adrian Chadd wrote, On 12/30/2013 22:17:
> On 17 December 2013 22:41,  <dt71@gmx.com> wrote:
>> It fixes non-deterministic lockups when the (old, drm1) r300 drivers are
>> used.
>>
>> According to John Baldwin [1]: "The drm code is doing a copyin() while
>> holding a mutex (which is not allowed)." The latest version of the patch
>> (also the one I used for years) is at [2], linked from [3].
>
> Hm. Well, can we add some lock assertions to the dri code to panic
> whenever this is done?

Oops, I meant panics, not lockups. The kernel panics exactly because -- as I gather -- the assertions are already there.

There are lockup issues even with the patch applied (for the most part, only when using, in Xorg.conf: Option "AccelMethod" "EXA").