I am now seeing this bug with the Precise linux-3.2.0-60 package on the same hardware.
I will try to create a lab-conditions reproduction of the issue to test the 3.11.10.6 kernel, but so far the problem only manifests on my production workload and/or production hardware.
I am now seeing this bug with the Precise linux-3.2.0-60 package on the same hardware.
I will try to create a lab-conditions reproduction of the issue to test the 3.11.10.6 kernel, but so far the problem only manifests on my production workload and/or production hardware.