Felix Leimbach wrote:
It's exactly the same CPU I have.
Interesting: Since two months I'm running on 2 Shanghai Quad-Cores
instead and the problem is definitely gone.
The rest of the hardware as well as the whole software-stack remained
unchanged.
That should confirm what we assumed already.
For me, it turned out that KVM I was running (coming with Proxmox VE)
had a "fairsched" patch (OpenVZ-related) which caused this broken behaviour.
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
