From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946119Ab3BHImj (ORCPT ); Fri, 8 Feb 2013 03:42:39 -0500 Received: from mail-ea0-f177.google.com ([209.85.215.177]:34875 "EHLO mail-ea0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1946079Ab3BHImi (ORCPT ); Fri, 8 Feb 2013 03:42:38 -0500 Date: Fri, 8 Feb 2013 09:44:48 +0100 From: Daniel Vetter To: Sergey Senozhatsky Cc: Andreas Bombe , Dave Airlie , Linux Kernel , dri-devel@lists.freedesktop.org, Dave Jones Subject: Re: radeon causing sleeping function called from invalid context Message-ID: <20130208084448.GP5813@phenom.ffwll.local> Mail-Followup-To: Sergey Senozhatsky , Andreas Bombe , Dave Airlie , Linux Kernel , dri-devel@lists.freedesktop.org, Dave Jones References: <20130113012717.GA2673@redhat.com> <20130113113820.GA2503@swordfish> <20130207215301.GA11773@amos.fritz.box> <20130208074742.GA2357@swordfish.minsk.epam.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130208074742.GA2357@swordfish.minsk.epam.com> X-Operating-System: Linux phenom 3.7.0-rc4+ User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 08, 2013 at 10:47:42AM +0300, Sergey Senozhatsky wrote: > On (02/07/13 22:53), Andreas Bombe wrote: > > On Sun, Jan 13, 2013 at 02:38:20PM +0300, Sergey Senozhatsky wrote: > > > On (01/12/13 20:27), Dave Jones wrote: > > > > BUG: sleeping function called from invalid context at mm/slub.c:925 > > > > in_atomic(): 1, irqs_disabled(): 0, pid: 566, name: Xorg > > > > INFO: lockdep is turned off. > > > > Pid: 566, comm: Xorg Not tainted 3.8.0-rc3+ #49 > > > > Call Trace: > > > > [] __might_sleep+0x141/0x200 > > > > [] kmem_cache_alloc_trace+0x4b/0x2a0 > > > > [] ttm_bo_move_accel_cleanup+0x1d3/0x330 [ttm] > > > > [] radeon_move_blit.isra.4+0xf8/0x160 [radeon] > > > > [] radeon_bo_move+0xb0/0x1f0 [radeon] > > > > [] ttm_bo_handle_move_mem+0x27d/0x5d0 [ttm] > > > > [] ? get_parent_ip+0x11/0x50 > > > > [] ttm_bo_move_buffer+0x127/0x140 [ttm] > > > > [] ? ttm_eu_list_ref_sub+0x3d/0x60 [ttm] > > > > [] ttm_bo_validate+0xa2/0x120 [ttm] > > > > [] radeon_bo_list_validate+0x75/0x90 [radeon] > > > > [] radeon_cs_ioctl+0x582/0x950 [radeon] > > > > [] drm_ioctl+0x4d3/0x580 [drm] > > > > [] ? radeon_cs_finish_pages+0xf0/0xf0 [radeon] > > > > [] do_vfs_ioctl+0x99/0x5a0 > > > > [] ? file_has_perm+0x97/0xb0 > > > > [] ? rcu_eqs_exit+0x65/0xb0 > > > > [] sys_ioctl+0x91/0xb0 > > > > [] tracesys+0xdd/0xe2 > > > > > > > > > > I see lots of these [mostly from page fault], the following one (quick and dirty) works for me. > > > > Is that patch or any other fix being picked up? It's over three weeks > > now and I'm still seeing those BUGs with the latest 3.8-rc. > > > > None that I'm aware of. Either this one https://patchwork.kernel.org/patch/2094501/ or a bit an older approach here https://patchwork.kernel.org/patch/1972071/ should fix this. /me looks at Dave Cheers, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch