l.org; linux-rt-us...@vger.kernel.org
>Subject: Re: BUG: unable to handle kernel NULL pointer dereference at
>000000000038 !//RE: kernel BUG at kernel/locking/rtmutex.c:1027
>
>On Tue, Jun 27, 2017 at 05:47:41AM +, Feng Feng24 Liu wrote:
>> Hi, Julia
>> Thanks for your kin
On Tue, Jun 27, 2017 at 05:47:41AM +, Feng Feng24 Liu wrote:
> Hi, Julia
> Thanks for your kindly hit. I will try this patch
> The problem is accidental. I will try to reproduce it.
> BTW, could you help to give the link about the emails which
> discuss about " nsfs: mar
l.org; t...@hp.com
>Subject: Re: BUG: unable to handle kernel NULL pointer dereference at
>00000038 !//RE: kernel BUG at kernel/locking/rtmutex.c:1027
>
>On Mon, Jun 26, 2017 at 04:54:36PM +0200, Sebastian Andrzej Siewior wrote:
>> On 2017-06-26 10:24:18 [-0400], Steven Ros
h; linux-kernel@vger.kernel.org;
>linux-rt-us...@vger.kernel.org; t...@hp.com
>Subject: Re: BUG: unable to handle kernel NULL pointer dereference at
>000000000038 !//RE: kernel BUG at kernel/locking/rtmutex.c:1027
>
>On 2017-06-26 10:24:18 [-0400], Steven Rostedt wrote:
>> > CP
rt-us...@vger.kernel.org; t...@hp.com
>Subject: Re: BUG: unable to handle kernel NULL pointer dereference at
>000000000038 !//RE: kernel BUG at kernel/locking/rtmutex.c:1027
>
>On Mon, 26 Jun 2017 06:33:29 +
>Feng Feng24 Liu wrote:
>
>> Hi, dear RT experts
>>
On Mon, Jun 26, 2017 at 04:54:36PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-06-26 10:24:18 [-0400], Steven Rostedt wrote:
> > > CPU: 17 PID: 1738811 Comm: ip Not tainted 4.4.70-thinkcloud-nfv #1
> > > Hardware name: LENOVO System x3650 M5: -[8871AC1]-/01GR174, BIOS
> > > -[TCE124M-2.10]
On 2017-06-26 10:24:18 [-0400], Steven Rostedt wrote:
> > CPU: 17 PID: 1738811 Comm: ip Not tainted 4.4.70-thinkcloud-nfv #1
> > Hardware name: LENOVO System x3650 M5: -[8871AC1]-/01GR174, BIOS
> > -[TCE124M-2.10]- 06/23/2016
> > task: 881cda2c27c0 ti: 881ea0538000 task.ti: 881ea053
On Mon, 26 Jun 2017 06:33:29 +
Feng Feng24 Liu wrote:
> Hi, dear RT experts
> Thanks a lot!
> I update our kernel to 4.4.70-rt83 as your suggestion. The incorrect
> deadlock detection problem has been fixed in this version.
>
> But I found there is another BUG in 4.
Hi, Steve & dear RT experts:
Thanks a lot!
I update our kernel to 4.4.70-rt83, which is the latest version. I
found the incorrect deadlock detection problem(kernel BUG at
kernel/locking/rtmutex.c:1027 ) has been fixed in this version.
But I found ther
:58 node-1 kernel: [45782.933537] [] ?
____fput+0xe/0x10
<4>Jun 24 10:16:58 node-1 kernel: [45782.933539] [] ?
task_work_run+0x86/0xb0
<4>Jun 24 10:16:58 node-1 kernel: [45782.933543] [] ?
exit_to_usermode_loop+0xa2/0xd7
<4>Jun 24 10:16:58 node-1 kernel: [45782.933546] [] ?
On Thu, 8 Jun 2017 07:01:08 +
Feng Feng24 Liu 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 giv
On 2017-06-08 09:31:39 [+0200], Mike Galbraith wrote:
> On Thu, 2017-06-08 at 07:01 +, Feng Feng24 Liu wrote:
> >
> > Our kernel version is: kernel4.4.6-rt14
> >
>
> Latest 4.4-rt is 4.4.70-rt83...
Exactly. Please test it with the latest v4.4 RT tree.
https://www.kernel.org/pu
On Thu, 2017-06-08 at 07:01 +, Feng Feng24 Liu wrote:
>
> Our kernel version is: kernel4.4.6-rt14
>
Latest 4.4-rt is 4.4.70-rt83...
[51893.656767]
>[] ? _raw_spin_unlock_irqrestore+0x20/0x50
>[51893.656768] [] inet_recvmsg+0x90/0xb0 [51893.656769]
>[] sock_recvmsg+0x3b/0x50 [51893.656770]
>[] sock_read_iter+0x88/0xd0 [51893.656772]
>[] __vfs_read+0xaa/0xe0 [51893.656774] []
>vfs_read+0x82/0x110 [51893.656775]
]
[51893.656778]
[51893.656796] ------------[ cut here ]----
[51893.656796] kernel BUG at kernel/locking/rtmutex.c:1027!
[51893.656798] invalid opcode: [#1] PREEMPT SMP
[51893.656822] Modules linked in: xt_REDIRECT nf_nat_redirect xt_nat xt_mark
ip6table_raw ip6table_mangle ip6
15 matches
Mail list logo