Mir

mir_proving_server with INTEL_DEBUG=perf says: CPU mapping a busy miptree BO stalled and took 0.078 ms.

Bug #1583959 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
New
Undecided
Unassigned
mir (Ubuntu)
New
Undecided
Unassigned

Bug Description

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.

Tags: performance
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.
description: updated
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.
Revision history for this message
Michał Sawicz (saviq) wrote :

Syncing task from Mir.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.