Date: Mon, 08 Nov 2010 14:07:43 +0200 From: Andriy Gapon <avg@freebsd.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-x11@freebsd.org, freebsd-current@freebsd.org Subject: Re: radeon_cp_texture: page fault with non-sleepable locks held Message-ID: <4CD7E80F.4090100@freebsd.org> In-Reply-To: <20101108120403.GC2392@deviant.kiev.zoral.com.ua> References: <4CD3B1D2.30003@icyb.net.ua> <4CD7E401.1010206@freebsd.org> <20101108120403.GC2392@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
on 08/11/2010 14:04 Kostik Belousov said the following: > On Mon, Nov 08, 2010 at 01:50:25PM +0200, Andriy Gapon wrote: >> on 05/11/2010 09:27 Andriy Gapon said the following: >>> >>> I use FreeSBD head and KDE 4 with all the bells and whistles enabled. >>> Apparently recent KDE update has enabled even more of them, because I started to >>> have panics with a kernel that has INVARIANTS and WITNESS enabled. >> >> I tried to solve the problem by changing drmdev from mutex to sx: >> http://people.freebsd.org/~avg/drm-sx.diff > I remember that drm lock can be acquired from the interrupt thread, if > the card supports interrupts. Changing it to sx cannot work then, because > interrupt threads cannot sleep. Most likely, you are getting around it > since r600 not yet used interrupts on FreeBSD. > > I think the solution is to drop drm lock around copyin. Kostik, thanks a lot for the help! Are familiar enough with the code to tell if drmdev is always held at that place? Or should I first check if it's actually owned and drop/reacquire it accordingly? -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CD7E80F.4090100>