From: Steven Rostedt <rostedt@goodmis.org>
To: Feng Feng24 Liu <liufeng24@lenovo.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"tmac@hp.com" <tmac@hp.com>, Tong Tong3 Li <litong3@lenovo.com>
Subject: Re: kernel BUG at kernel/locking/rtmutex.c:1027
Date: Thu, 8 Jun 2017 09:45:45 -0400 [thread overview]
Message-ID: <20170608094545.67901a4f@gandalf.local.home> (raw)
In-Reply-To: <2B18E8E1DDAE074A82D1060396451DAE263C7C1A@CNMAILEX04.lenovo.com>
On Thu, 8 Jun 2017 07:01:08 +0000
Feng Feng24 Liu <liufeng24@lenovo.com> wrote:
> Hi, T Makphaibulchoke & Steve
> I found that you discuss about " kernel BUG at kernel/locking/rtmutex.c:997 " at
> https://groups.google.com/forum/#!topic/fa.linux.kernel/aV2peeXs71E
>
> Could you help to give some advice?
> Our kernel version is: kernel4.4.6-rt14
> Whether our problem ,which I describe above, is the same problem as " kernel BUG at kernel/locking/rtmutex.c:997"?
> And why is the patch "[PATCH 3.14.25-rt22 1/2] rtmutex Real-Time Linux: Fixing kernel BUG at kernel/locking/rtmutex.c:997!" not apply to the upsteam or rt-patches?
You mean commit 8fe55d0c10959a4f2b6e9efe57a8698ce2fa2f33 that was added
in v4.4.50-rt63?
-- Steve
>
> Thanks a lot
>
> Thanks
> Feng
>
next prev parent reply other threads:[~2017-06-08 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 7:01 kernel BUG at kernel/locking/rtmutex.c:1027 Feng Feng24 Liu
2017-06-08 7:31 ` Mike Galbraith
2017-06-08 8:03 ` Sebastian Andrzej Siewior
2017-06-08 13:45 ` Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-06 15:18 Feng Feng24 Liu
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=20170608094545.67901a4f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=litong3@lenovo.com \
--cc=liufeng24@lenovo.com \
--cc=tmac@hp.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;
as well as URLs for NNTP newsgroup(s).