Date: Fri, 1 Oct 2004 16:00:47 GMT From: Vaclav Rehak <vasek@openbsd.cz> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/72224: umass devices not working under X Message-ID: <200410011600.i91G0luR080273@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410011600.i91G0luR080273>