Activity log for bug #1583959

Date Who What changed Old value New value Message
2016-05-20 08:26:56 Daniel van Vugt bug added bug
2016-05-20 08:27:44 Daniel van Vugt summary Mir servers with INTEL_DEBUG=perf say: CPU mapping a busy miptree BO stalled and took 0.078 ms. mir_proving_server with INTEL_DEBUG=perf say: CPU mapping a busy miptree BO stalled and took 0.078 ms.
2016-05-20 08:28:01 Daniel van Vugt description Mir demo servers with INTEL_DEBUG=perf say this when some clients (hardware or software) run: CPU mapping a busy miptree BO stalled and took 0.078 ms. CPU mapping a busy miptree BO stalled and took 0.038 ms. CPU mapping a busy miptree BO stalled and took 0.005 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.000 ms. CPU mapping a busy miptree BO stalled and took 0.000 ms. CPU mapping a busy miptree BO stalled and took 0.000 ms. CPU mapping a busy miptree BO stalled and took 0.000 ms. CPU mapping a busy miptree BO stalled and took 0.080 ms. CPU mapping a busy miptree BO stalled and took 0.128 ms. CPU mapping a busy miptree BO stalled and took 0.005 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.004 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.004 ms. CPU mapping a busy miptree BO stalled and took 0.146 ms. CPU mapping a busy miptree BO stalled and took 0.089 ms. CPU mapping a busy miptree BO stalled and took 0.008 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.001 ms. CPU mapping a busy miptree BO stalled and took 0.001 ms. CPU mapping a busy miptree BO stalled and took 0.001 ms. CPU mapping a busy miptree BO stalled and took 0.000 ms. CPU mapping a busy miptree BO stalled and took 0.001 ms. mir_proving_server with INTEL_DEBUG=perf says this when some clients (hardware or software) run: CPU mapping a busy miptree BO stalled and took 0.078 ms. CPU mapping a busy miptree BO stalled and took 0.038 ms. CPU mapping a busy miptree BO stalled and took 0.005 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.000 ms. CPU mapping a busy miptree BO stalled and took 0.000 ms. CPU mapping a busy miptree BO stalled and took 0.000 ms. CPU mapping a busy miptree BO stalled and took 0.000 ms. CPU mapping a busy miptree BO stalled and took 0.080 ms. CPU mapping a busy miptree BO stalled and took 0.128 ms. CPU mapping a busy miptree BO stalled and took 0.005 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.004 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.004 ms. CPU mapping a busy miptree BO stalled and took 0.146 ms. CPU mapping a busy miptree BO stalled and took 0.089 ms. CPU mapping a busy miptree BO stalled and took 0.008 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.002 ms. CPU mapping a busy miptree BO stalled and took 0.001 ms. CPU mapping a busy miptree BO stalled and took 0.001 ms. CPU mapping a busy miptree BO stalled and took 0.001 ms. CPU mapping a busy miptree BO stalled and took 0.000 ms. CPU mapping a busy miptree BO stalled and took 0.001 ms.
2016-05-20 08:28:08 Daniel van Vugt summary mir_proving_server with INTEL_DEBUG=perf say: CPU mapping a busy miptree BO stalled and took 0.078 ms. mir_proving_server with INTEL_DEBUG=perf says: CPU mapping a busy miptree BO stalled and took 0.078 ms.