From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andrew James Wade <andrew.j.wade@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Badness in __mutex_unlock_slowpath
Date: Sun, 8 Jan 2006 02:43:15 -0500 [thread overview]
Message-ID: <200601080246_MC3-1-B57D-BAA5@compuserve.com> (raw)
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
next reply other threads:[~2006-01-08 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 7:43 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-07 13:22 2.6.15-mm2 Andrew Morton
2006-01-07 20:51 ` Badness in __mutex_unlock_slowpath Andrew James Wade
2006-01-07 21:13 ` Arjan van de Ven
2006-01-08 8:53 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200601080246_MC3-1-B57D-BAA5@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=andrew.j.wade@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®