From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stan Hu <stanhu@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: help with diagnosing kernel oops in __mutex_lock_slowpath
Date: Thu, 1 Nov 2012 17:14:29 -0700 [thread overview]
Message-ID: <20121102001429.GA2129@kroah.com> (raw)
In-Reply-To: <CAMBWrQm6CacSoUxZdNA9XPhDMqyAt2R15ZXxpCLEZcRvEeRiCg@mail.gmail.com>
On Thu, Nov 01, 2012 at 03:02:45PM -0700, Stan Hu wrote:
> Hello,
>
> I'm getting this kernel oops sporadically with a custom Cortex-A8 ARM
> board with a Linux 3.2.28 kernel. The system is booting off an SD
> card; interestingly this failure doesn't seem to happen when I boot
> from NAND flash. I would say 1 out 10 times it fails with a similar
> backtrace. Does anyone have any clue why this might be happening?
Does this also happen on the 3.6 kernel, or 3.7-rc3?
thanks,
greg k-h
next prev parent reply other threads:[~2012-11-02 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMBWrQ=Xrp-_opV0ej4rn20p3yTUP0TmYQHr5nG79szC0=WUDA@mail.gmail.com>
2012-11-01 22:02 ` help with diagnosing kernel oops in __mutex_lock_slowpath Stan Hu
2012-11-02 0:14 ` Greg Kroah-Hartman [this message]
2012-11-02 0:23 ` Stan Hu
2012-11-02 0:58 ` Greg Kroah-Hartman
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=20121102001429.GA2129@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stanhu@gmail.com \
/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