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:58:52 -0700 [thread overview]
Message-ID: <20121102005852.GA2575@kroah.com> (raw)
In-Reply-To: <CAMBWrQmQqF7yjmZWkVFbjWrPUane-tB2sm6BCgn-x4QnXWYVgA@mail.gmail.com>
On Thu, Nov 01, 2012 at 05:23:48PM -0700, Stan Hu wrote:
> Unfortunately, with this board I am using, it would be a significant
> effort for me to get 3.6 or 3.7 running. Do you have any suggestions
> of what I should look for in the 3.2 kernel?
Why is that, because companies don't have their board support upstream?
If you are dealing with a non-stock kernel.org kernel, there's not much
we can do to help, try asking the company that provided that patches you
are using.
And no, I don't what to look for for this, sorry, 3.2 was a few tens of
thousands of patches ago :)
good luck,
greg k-h
prev parent reply other threads:[~2012-11-02 0:58 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
2012-11-02 0:23 ` Stan Hu
2012-11-02 0:58 ` Greg Kroah-Hartman [this message]
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=20121102005852.GA2575@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