[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170608094545.67901a4f@gandalf.local.home>
Date: Thu, 8 Jun 2017 09:45:45 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Feng Feng24 Liu <liufeng24@...ovo.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-rt-users@...r.kernel.org" <linux-rt-users@...r.kernel.org>,
"tmac@...com" <tmac@...com>, Tong Tong3 Li <litong3@...ovo.com>
Subject: Re: kernel BUG at kernel/locking/rtmutex.c:1027
On Thu, 8 Jun 2017 07:01:08 +0000
Feng Feng24 Liu <liufeng24@...ovo.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
>
Powered by blists - more mailing lists