Comment 3 for bug 1717796

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

We need some stack information to help us determine the cause of the CPU spikes.

1. Download the attached dstack script to your home directory.
2. Log in to a virtual terminal (Ctrl+Alt+F1), and switch back (Ctrl+Alt+F7)
3. When the spike happens, switch to Ctrl+Alt+F1 and run this:
    sudo -s
    sh ./dstack bluetoothd >> stacks.txt
    sh ./dstack bluetoothd >> stacks.txt
    sh ./dstack bluetoothd >> stacks.txt
    sh ./dstack bluetoothd >> stacks.txt
    sh ./dstack bluetoothd >> stacks.txt
   (yes, five times)
4. Attach the resulting stacks.txt to this bug.