l.org; linux-rt-us...@vger.kernel.org
>Subject: Re: BUG: unable to handle kernel NULL pointer dereference at
>00000038 !//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
l.org; linux-rt-us...@vger.kernel.org
>Subject: Re: BUG: unable to handle kernel NULL pointer dereference at
>00000038 !//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
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:
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:
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
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
>00000038 !//RE: kernel BUG at kernel/locking/rtmutex.c:1027
>
>On 2017-06-26 10:24:18 [-0400], Steven Rostedt wrote:
>> > CP
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
>00000038 !//RE: kernel BUG at kernel/locking/rtmutex.c:1027
>
>On 2017-06-26 10:24:18 [-0400], Steven Rostedt wrote:
>> > CP
...@vger.kernel.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, 26 Jun 2017 06:33:29 +
>Feng Feng24 Liu <liufen...@lenovo.com> wrote:
>
>> Hi, dear R
...@vger.kernel.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, 26 Jun 2017 06:33:29 +
>Feng Feng24 Liu wrote:
>
>> Hi, dear RT experts
>> Than
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
> > >
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
> > >
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:
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:
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
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
:58 node-1 kernel: [45782.933536] [] ?
__fput+0x16a/0x1e0
<4>Jun 24 10:16: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_userm
:58 node-1 kernel: [45782.933536] [] ?
__fput+0x16a/0x1e0
<4>Jun 24 10:16: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_l
: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] [] ?
: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
>
>
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
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.
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.
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...
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...
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:
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:
28 matches
Mail list logo