![]() | |||||||||||||
Messages in this thread |
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 > [<c03538e8>] __mutex_unlock_slowpath+0x56/0x1a2 > [<c0302f08>] snd_pcm_oss_write+0x0/0x1e0 > [<c0302f3c>] snd_pcm_oss_write+0x34/0x1e0 > [<c0302f08>] snd_pcm_oss_write+0x0/0x1e0 > [<c0148221>] vfs_write+0x83/0x122 > [<c0148a36>] sys_write+0x3c/0x63 > [<c0102ba3>] 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/ | ||||||||||||
| Last update: 2006-01-08 07:50 [from the cache] ©2003-2008 | |||||||||||||