From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [bug report] dead lock (?) occur on ap325 board
Date: Mon, 26 Jan 2009 02:20:56 +0000 [thread overview]
Message-ID: <20090126022055.GE17836@linux-sh.org> (raw)
In-Reply-To: <uprie4cmj.wl%morimoto.kuninori@renesas.com>
On Fri, Jan 23, 2009 at 06:04:20PM +0900, morimoto.kuninori@renesas.com wrote:
> I found dead lock (? freeze?) bug again on
> ------------------------------------------------
> commit 77ba93a7ac5fb0d9338bffbf97c787b8efe00806
> Author: Paul Mundt <lethal@linux-sh.org>
> Date: Mon Dec 8 11:25:50 2008 +0900
>
> sh: Fix up the SH-4A mutex fastpath semantics.
> ------------------------------------------------
>
> I get dead lock even if following patch is added
> (this bug will be fixed on 06be3724548a443a99d703ff79f43d6f1e2975f0)
> ----------------
> Author: Paul Mundt <lethal@linux-sh.org>
> Date: Mon Dec 8 17:01:40 2008 +0900
>
> sh: Fix an off-by-1 check in __mutex_fastpath_unlock().
> ----------------
>
> c6f17cb2272121475c87592560534b157b17544e is OK for me.
> (but YOSHII-san's patch (3b041227f7ef7c7e97f205c68c6069c0c62e5204)
> is still needed.)
>
I haven't been able to reproduce this yet, but it would be helpful to
know precisely where your lock up occurs. If you aren't using JTAG, you
can try sending an NMI, or send a register and/or stacktrace request via
magic sysrq.
next prev parent reply other threads:[~2009-01-26 2:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 9:04 [bug report] dead lock (?) occur on ap325 board morimoto.kuninori
2009-01-26 2:20 ` Paul Mundt [this message]
2009-01-26 5:01 ` morimoto.kuninori
2009-01-27 8:26 ` morimoto.kuninori
2009-01-27 8:32 ` Paul Mundt
2009-01-27 8:46 ` morimoto.kuninori
2009-01-27 8:49 ` Paul Mundt
2009-01-28 1:25 ` morimoto.kuninori
2009-01-28 9:29 ` Takashi Yoshii
2009-01-28 10:03 ` Paul Mundt
2009-01-29 0:34 ` yoshii.takashi
2009-01-29 23:54 ` morimoto.kuninori
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=20090126022055.GE17836@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
/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