From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755231AbZBXB4l (ORCPT ); Mon, 23 Feb 2009 20:56:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753810AbZBXB4c (ORCPT ); Mon, 23 Feb 2009 20:56:32 -0500 Received: from cn.fujitsu.com ([222.73.24.84]:65291 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753704AbZBXB4b (ORCPT ); Mon, 23 Feb 2009 20:56:31 -0500 Message-ID: <49A353BD.40000@cn.fujitsu.com> Date: Tue, 24 Feb 2009 09:56:13 +0800 From: Wang Chen User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: "Rafael J. Wysocki" CC: Linux Kernel Mailing List , Kernel Testers List , Dave Airlie , Eric Anholt Subject: Re: [Bug #12419] possible circular locking dependency on i915 dma References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Rafael J. Wysocki said the following on 2009-2-24 5:48: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.28. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12419 > Subject : possible circular locking dependency on i915 dma > Submitter : Wang Chen > Date : 2009-01-08 14:11 (47 days old) > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=546b0974c39657017407c86fe79811100b60700d > References : http://marc.info/?l=linux-kernel&m=123142399720125&w=4 > not changed. ======================================================= [ INFO: possible circular locking dependency detected ] 2.6.29-rc6-default #165 ------------------------------------------------------- X/3940 is trying to acquire lock: (&mm->mmap_sem){----}, at: [] might_fault+0x42/0x7e but task is already holding lock: (&dev->struct_mutex){--..}, at: [] i915_cmdbuffer+0xf4/0x411 [i915] which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&dev->struct_mutex){--..}: [] validate_chain+0x8be/0xbb5 [] __lock_acquire+0x66f/0x6f9 [] lock_acquire+0x5b/0x77 [] mutex_lock_nested+0xdb/0x244 [] drm_vm_open+0x25/0x37 [drm] [] dup_mm+0x247/0x2f2 [] copy_process+0x98c/0xfeb [] do_fork+0x120/0x29c [] sys_clone+0x25/0x2a [] sysenter_do_call+0x12/0x31 [] 0xffffffff -> #1 (&mm->mmap_sem/1){--..}: [] validate_chain+0x8be/0xbb5 [] __lock_acquire+0x66f/0x6f9 [] lock_acquire+0x5b/0x77 [] down_write_nested+0x32/0x4f [] dup_mm+0xa5/0x2f2 [] copy_process+0x98c/0xfeb [] do_fork+0x120/0x29c [] sys_clone+0x25/0x2a [] sysenter_do_call+0x12/0x31 [] 0xffffffff -> #0 (&mm->mmap_sem){----}: [] validate_chain+0x5c9/0xbb5 [] __lock_acquire+0x66f/0x6f9 [] lock_acquire+0x5b/0x77 [] might_fault+0x5f/0x7e [] i915_emit_box+0x1d/0x20c [i915] [] i915_cmdbuffer+0x165/0x411 [i915] [] drm_ioctl+0x1a6/0x21b [drm] [] vfs_ioctl+0x3d/0x50 [] do_vfs_ioctl+0x41b/0x483 [] sys_ioctl+0x40/0x5a [] sysenter_do_call+0x12/0x31 [] 0xffffffff