Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750719AbWJJNKO (ORCPT ); Tue, 10 Oct 2006 09:10:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750721AbWJJNKO (ORCPT ); Tue, 10 Oct 2006 09:10:14 -0400 Received: from ug-out-1314.google.com ([66.249.92.174]:64450 "EHLO ug-out-1314.google.com") by vger.kernel.org with ESMTP id S1750719AbWJJNKM (ORCPT ); Tue, 10 Oct 2006 09:10:12 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LTxXUHJ981xfqXnsh9pdFUkkqNY03dnC484YwpUl61cZ9FxtMmMiyR92bVUTHwJnEYBHU303o0cbcEgBAlmUeBy1FKnja4ReoX3W+7jb56uj2aRYVUruyhQOOUx6EQ0J+jPc24E1Heho3e5ZJjbVtzUXNdE0jbWlqdh3LTlXSE0= Message-ID: <6bffcb0e0610100610p6eb65726of92b85f7d49e80bb@mail.gmail.com> Date: Tue, 10 Oct 2006 15:10:10 +0200 From: "Michal Piotrowski" To: "Andrew Morton" Subject: Re: 2.6.19-rc1-mm1 Cc: "Pavel Machek" , "Rafael J. Wysocki" , linux-kernel@vger.kernel.org, "Neil Brown" In-Reply-To: <20061010000928.9d2d519a.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061010000928.9d2d519a.akpm@osdl.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4225 Lines: 115 Hi, On 10/10/06, Andrew Morton wrote: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc1/2.6.19-rc1-mm1/ > Kernel 2.6.19-rc1-mm1 + Neil's avoid_lockdep_warning_in_md.patch (http://www.ussg.iu.edu/hypermail/linux/kernel/0610.1/0642.html) (I'll try to reproduce this without Neil's patch). echo shutdown > /sys/power/disk; echo disk > /sys/power/state ======================================================= [ INFO: possible circular locking dependency detected ] 2.6.19-rc1-mm1 #4 ------------------------------------------------------- bash/2404 is trying to acquire lock: ((cpu_chain).rwsem){..--}, at: [] blocking_notifier_call_chain+0x11/0x2d but task is already holding lock: (workqueue_mutex){--..}, at: [] mutex_lock+0x1c/0x1f which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (workqueue_mutex){--..}: [] add_lock_to_list+0x5c/0x7a [] __lock_acquire+0x9f3/0xaef [] lock_acquire+0x71/0x91 [] __mutex_lock_slowpath+0xd2/0x2f1 [] mutex_lock+0x1c/0x1f [] workqueue_cpu_callback+0x109/0x1ff [] notifier_call_chain+0x20/0x31 [] blocking_notifier_call_chain+0x1d/0x2d [] _cpu_down+0x48/0x1ff [] disable_nonboot_cpus+0x9b/0x12f [] prepare_processes+0xf/0x73 [] pm_suspend_disk+0xa/0x11c [] enter_state+0x5a/0x185 [] state_store+0x86/0x9c [] subsys_attr_store+0x20/0x25 [] sysfs_write_file+0xaa/0xd3 [] vfs_write+0xcd/0x179 [] sys_write+0x3b/0x71 [] sysenter_past_esp+0x56/0x8d [] 0xffffffff -> #0 ((cpu_chain).rwsem){..--}: [] print_circular_bug_tail+0x30/0x64 [] __lock_acquire+0x92a/0xaef [] lock_acquire+0x71/0x91 [] down_read+0x28/0x3c [] blocking_notifier_call_chain+0x11/0x2d [] _cpu_down+0x168/0x1ff [] disable_nonboot_cpus+0x9b/0x12f [] prepare_processes+0xf/0x73 [] pm_suspend_disk+0xa/0x11c [] enter_state+0x5a/0x185 [] state_store+0x86/0x9c [] subsys_attr_store+0x20/0x25 [] sysfs_write_file+0xaa/0xd3 [] vfs_write+0xcd/0x179 [] sys_write+0x3b/0x71 [] sysenter_past_esp+0x56/0x8d [] 0xffffffff other info that might help us debug this: 2 locks held by bash/2404: #0: (cpu_add_remove_lock){--..}, at: [] mutex_lock+0x1c/0x1f #1: (workqueue_mutex){--..}, at: [] mutex_lock+0x1c/0x1f stack backtrace: [] dump_trace+0x64/0x1cd [] show_trace_log_lvl+0x12/0x25 [] show_trace+0xd/0x10 [] dump_stack+0x19/0x1b [] print_circular_bug_tail+0x59/0x64 [] __lock_acquire+0x92a/0xaef [] lock_acquire+0x71/0x91 [] down_read+0x28/0x3c [] blocking_notifier_call_chain+0x11/0x2d [] _cpu_down+0x168/0x1ff [] disable_nonboot_cpus+0x9b/0x12f [] prepare_processes+0xf/0x73 [] pm_suspend_disk+0xa/0x11c [] enter_state+0x5a/0x185 [] state_store+0x86/0x9c [] subsys_attr_store+0x20/0x25 [] sysfs_write_file+0xaa/0xd3 [] vfs_write+0xcd/0x179 [] sys_write+0x3b/0x71 [] sysenter_past_esp+0x56/0x8d DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d Leftover inexact backtrace: ======================= config & dmesg http://www.stardust.webpages.pl/files/tbf/euridica/2.6.19-rc1-mm1/ Regards, Michal -- Michal K. K. Piotrowski LTG - Linux Testers Group (http://www.stardust.webpages.pl/ltg/) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/