Soft Lockup in "__udp4_lib_lookup", Maybe a GCC's bug

2017-04-05 Thread Cai, Jason
Hi guys, I'm using linux-3.2, yes, it's pretty old I know, and I'm going to move on a latest stable version. I hit a soft lockup issue in function `__udp4_lib_lookup`. And it turns out that the soft lockup results from that it got a hlist_nulls_node from a hash slot, but that hlist_nulls_node

Soft Lockup in "__udp4_lib_lookup", Maybe a GCC's bug

2017-04-05 Thread Cai, Jason
Hi guys, I'm using linux-3.2, yes, it's pretty old I know, and I'm going to move on a latest stable version. I hit a soft lockup issue in function `__udp4_lib_lookup`. And it turns out that the soft lockup results from that it got a hlist_nulls_node from a hash slot, but that hlist_nulls_node

RE: Linux 3.2: FPU Issue in execve with Intel E5-2620v3 and E7-4880v2

2017-03-22 Thread Cai, Jason
[mailto:gre...@linuxfoundation.org] Sent: 2017年3月22日 14:10 To: Cai, Jason <jason@emc.com> Cc: sta...@vger.kernel.org; kernelnewb...@nl.linux.org; linux-kernel@vger.kernel.org Subject: Re: Linux 3.2: FPU Issue in execve with Intel E5-2620v3 and E7-4880v2 On Wed, Mar 22, 2017 at 01:58:58AM +000

RE: Linux 3.2: FPU Issue in execve with Intel E5-2620v3 and E7-4880v2

2017-03-22 Thread Cai, Jason
[mailto:gre...@linuxfoundation.org] Sent: 2017年3月22日 14:10 To: Cai, Jason Cc: sta...@vger.kernel.org; kernelnewb...@nl.linux.org; linux-kernel@vger.kernel.org Subject: Re: Linux 3.2: FPU Issue in execve with Intel E5-2620v3 and E7-4880v2 On Wed, Mar 22, 2017 at 01:58:58AM +, Cai, Jason wrote

Linux 3.2: FPU Issue in execve with Intel E5-2620v3 and E7-4880v2

2017-03-21 Thread Cai, Jason
Dear Kernel Hackers, I'm Jason Cai, a kernel developer from Dell EMC. I hit the same issue as the one Lennart Sorensen sent at Dec 19, 2016. I narrow down the issue now. It seems that an unexpected DNA (Device not Available) may be triggered in the `execve` code path. Specifically, it exists

Linux 3.2: FPU Issue in execve with Intel E5-2620v3 and E7-4880v2

2017-03-21 Thread Cai, Jason
Dear Kernel Hackers, I'm Jason Cai, a kernel developer from Dell EMC. I hit the same issue as the one Lennart Sorensen sent at Dec 19, 2016. I narrow down the issue now. It seems that an unexpected DNA (Device not Available) may be triggered in the `execve` code path. Specifically, it exists