Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030496AbWAHHrp (ORCPT ); Sun, 8 Jan 2006 02:47:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030523AbWAHHrn (ORCPT ); Sun, 8 Jan 2006 02:47:43 -0500 Received: from liaag1aa.mx.compuserve.com ([149.174.40.27]:11393 "EHLO liaag1aa.mx.compuserve.com") by vger.kernel.org with ESMTP id S1030496AbWAHHrl (ORCPT ); Sun, 8 Jan 2006 02:47:41 -0500 Date: Sun, 8 Jan 2006 02:43:15 -0500 From: Chuck Ebbert <76306.1226@compuserve.com> Subject: Re: Badness in __mutex_unlock_slowpath To: Andrew James Wade Cc: Andrew Morton , Ingo Molnar , linux-kernel Message-ID: <200601080246_MC3-1-B57D-BAA5@compuserve.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1120 Lines: 32 In-Reply-To: <200601071551.20344.ajwade@cpe001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com> On Sat, 7 Jan 2006 at 15:51:19 -0500 Andrew James Wade wrote: > I got this when "amaroK" started playing: > > Badness in __mutex_unlock_slowpath at kernel/mutex.c:214 > [] __mutex_unlock_slowpath+0x56/0x1a2 > [] snd_pcm_oss_write+0x0/0x1e0 > [] snd_pcm_oss_write+0x34/0x1e0 > [] snd_pcm_oss_write+0x0/0x1e0 > [] vfs_write+0x83/0x122 > [] sys_write+0x3c/0x63 > [] sysenter_past_esp+0x54/0x75 The thread doing the unlock does not own the mutex. Same exact check is made a few lines later in debug_mutex_unlock(). And debugging gets turned off after the first debug message prints, so there could be other problems that are not reported. -- Chuck Currently reading: _Thud!_ by Terry Pratchett - 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/