From owner-freebsd-bugs@FreeBSD.ORG  Fri Oct  1 16:00:47 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 74EB316A4CE
	for <freebsd-bugs@hub.freebsd.org>;
	Fri,  1 Oct 2004 16:00:47 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6674E43D1D
	for <freebsd-bugs@hub.freebsd.org>;
	Fri,  1 Oct 2004 16:00:47 +0000 (GMT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i91G0lDl080274
	for <freebsd-bugs@freefall.freebsd.org>; Fri, 1 Oct 2004 16:00:47 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i91G0luR080273;
	Fri, 1 Oct 2004 16:00:47 GMT
	(envelope-from gnats)
Date: Fri, 1 Oct 2004 16:00:47 GMT
Message-Id: <200410011600.i91G0luR080273@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Vaclav Rehak <vasek@openbsd.cz>
Subject: Re: kern/72224: umass devices not working under X
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Vaclav Rehak <vasek@openbsd.cz>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2004 16:00:47 -0000

The following reply was made to PR kern/72224; it has been noted by GNATS.

From: Vaclav Rehak <vasek@openbsd.cz>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/72224: umass devices not working under X
Date: Fri, 1 Oct 2004 17:56:02 +0200

 On Fri, Oct 01, 2004 at 12:24:20PM +0200, Vaclav Rehak wrote:
 > 
 > uhub3: CANYON USB 2.0 Disk USB Embedded Hub, class 9/0, rev 2.00/0.01, addr 2
 > uhub3: 1 port with 0 removable, self powered
 > umass0: CANYON USB 2.0 Disk USB Mass Storage Device, rev 2.00/0.01, addr 3
 > da0 at umass-sim0 bus 0 target 0 lun 0
 > da0: <CANYON USB 2.0 Disk P1.0> Removable Direct Access SCSI-0 device 
 > da0: 1.000MB/s transfers
 > da0: 125MB (256000 512 byte sectors: 64H 32S/T 125C)
 > 
 > 	However, if I then start X, I can see following entries in dmesg
 > 
 > uhub3: at uhub1 port 1 (addr 2) disconnected
 
 > drm0: <ATI Radeon LW Mobility 7500 M7> port 0x3000-0x30ff mem 0xc0100000-0xc010ffff,0xe0000000-0xe7ffffff irq 11 at device 0.0 on pci1
 > info: [drm] Initialized radeon 1.11.0 20020828 on minor 0
 > error: [drm:pid500:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
 > error: [drm:pid500:radeon_unlock] *ERROR* Process 500 using kernel context 0
 
 After some more experimenting I realized that removing
        Load  "glx"
 option from my XF86Config makes umass devices work again.
 
 So the problem is apparently in the drm locking in /usr/src/sys/dev/drm/radeon_cp.c
 However, further investigation is beyond my skills.
 
 V.