Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751444AbYJNSSo (ORCPT ); Tue, 14 Oct 2008 14:18:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751348AbYJNSSh (ORCPT ); Tue, 14 Oct 2008 14:18:37 -0400 Received: from fg-out-1718.google.com ([72.14.220.153]:34484 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751307AbYJNSSg (ORCPT ); Tue, 14 Oct 2008 14:18:36 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=J4xIaa9Q2Oq7cCncIZd3ejls0dBQCt+yT5BfxMzHAlLIpClkiFghifUx/h2CuMDO9t rLBwKDKyl6fUvp+jmyg06pevvNUL86Vd84lsozndJ5mQPmCOTakHxIa/RDXKGKQYvgYX dktz0MlLrtoxoL0nZAn0fgLrCp34rECr6xobI= Date: Tue, 14 Oct 2008 20:17:28 +0200 From: Marcin Slusarz To: Dave Young Cc: linux-kernel@vger.kernel.org Subject: Re: lockdep warning: inconsistent hardirq-on-W -> in-hardirq-R Message-ID: <20081014181713.GA5623@joi> References: <48F42305.9000507@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48F42305.9000507@gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3408 Lines: 65 On Tue, Oct 14, 2008 at 12:41:41PM +0800, Dave Young wrote: > Hi, > > kernel built from today's linux-2.6 git, lockdep warnings as following: > > [ 52.984024] ================================= > [ 52.984030] [ INFO: inconsistent lock state ] > [ 52.984034] 2.6.27-smp #3 > [ 52.984037] --------------------------------- > [ 52.984040] inconsistent {hardirq-on-W} -> {in-hardirq-R} usage. > [ 52.984045] pulseaudio/3400 [HC1[1]:SC0[0]:HE0:SE1] takes: > [ 52.984048] (tasklist_lock){--?-}, at: [] run_posix_cpu_timers+0x52/0x9a0 > [ 52.984064] {hardirq-on-W} state was registered at: > [ 52.984068] [] mark_held_locks+0x30/0x80 > [ 52.984075] [] trace_hardirqs_on_caller+0x7a/0x140 > [ 52.984081] [] trace_hardirqs_on+0xb/0x10 > [ 52.984086] [] _spin_unlock_irq+0x22/0x30 > [ 52.984093] [] proc_clear_tty+0x45/0x60 > [ 52.984099] [] sys_setsid+0x96/0xa0 > [ 52.984105] [] syscall_call+0x7/0xb > [ 52.984111] [] 0xffffffff > [ 52.984124] irq event stamp: 636 > [ 52.984127] hardirqs last enabled at (635): [] trace_hardirqs_on_thunk+0xc/0x10 > [ 52.984135] hardirqs last disabled at (636): [] trace_hardirqs_off_thunk+0xc/0x18 > [ 52.984141] softirqs last enabled at (0): [] copy_process+0x26a/0x1160 > [ 52.984149] softirqs last disabled at (0): [<00000000>] 0x0 > [ 52.984155] > [ 52.984155] other info that might help us debug this: > [ 52.984160] no locks held by pulseaudio/3400. > [ 52.984162] > [ 52.984163] stack backtrace: > [ 52.984168] Pid: 3400, comm: pulseaudio Not tainted 2.6.27-smp #3 > [ 52.984171] Call Trace: > [ 52.984178] [] print_usage_bug+0x166/0x1a0 > [ 52.984183] [] mark_lock+0xa96/0xb10 > [ 52.984189] [] ? trace_hardirqs_off+0xb/0x10 > [ 52.984196] [] ? native_sched_clock+0x7f/0xb0 > [ 52.984202] [] __lock_acquire+0x552/0x9a0 > [ 52.984208] [] ? mark_held_locks+0x65/0x80 > [ 52.984213] [] lock_acquire+0x76/0xa0 > [ 52.984219] [] ? run_posix_cpu_timers+0x52/0x9a0 > [ 52.984224] [] _read_lock+0x36/0x60 > [ 52.984229] [] ? run_posix_cpu_timers+0x52/0x9a0 > [ 52.984234] [] run_posix_cpu_timers+0x52/0x9a0 > [ 52.984239] [] ? trace_hardirqs_off+0xb/0x10 > [ 52.984245] [] ? raise_softirq+0x65/0x90 > [ 52.984251] [] ? scheduler_tick+0x13c/0x1b0 > [ 52.984256] [] update_process_times+0x4f/0x60 > [ 52.984262] [] tick_sched_timer+0x50/0xc0 > [ 52.984266] [] ? tick_sched_timer+0x0/0xc0 > [ 52.984271] [] ? tick_sched_timer+0x0/0xc0 > [ 52.984276] [] __run_hrtimer+0x75/0x90 > [ 52.984282] [] hrtimer_interrupt+0x11d/0x180 > [ 52.984287] [] smp_apic_timer_interrupt+0x56/0x90 > [ 52.984293] [] ? trace_hardirqs_off_thunk+0xc/0x18 > [ 52.984298] [] apic_timer_interrupt+0x2d/0x34 Known bug, see: http://lkml.org/lkml/2008/10/13/368 Marcin -- 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/