This is often related to your network traffic and that most of the time Ifind the kernel just uses a single core to send or receive via your NIC. This can be adjusted like this so that multiple cores are used to send and receive data via your NIC (eth0). multicore eth0 RX #enable multicore echo f > /sys/class/net/eth0/queues/rx-0/rps_cpus # enable flow and entries cou........

It looks like this has something to do with APIC but I am not sure. I have similar CPUs with a different MB and BIOS that work fine on the same type of kernel. A lot of time the issue is because of the C-step setting in the BIOS. The same thing happened on the 2.6 kernel with Centos 6 but this is a homebrew 4.4 kernel soI am not sure why it is happening when even Centos 7 (3.2) kernel works OK. Solution - It comes down to the BIOS set........

This is obviously a bug in the r8169 kernel module and it seems to affect a lot of people. I upgraded to the latest kernel and hope this won't happen anymore, as it is a very serious error. This is especially serious for those who are running servers with this chipset, who can afford for the NIC to randomly go off-line for no apparent reason? [655548.189113] type=1505 audit(1277067560.902:5): operation="profile_load" name="/usr/bin/freshclam&q........