Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pipewire pipewire
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 576
    • Issues 576
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWirePipeWire
  • pipewirepipewire
  • Issues
  • #225
Closed
Open
Issue created Mar 28, 2020 by Mathieu Velten@MatMaul

Processor never goes in deeper C states when Pipewire is running

I noticed that as soon as PipeWire is running (usually after launching a flatpak app), my computer (X1 Carbon 6th generation, i7-8550U) no longer reach C-states deeper that C6 for the whole CPU package, with one of the core stalling that by never going under C8.

When PipeWire is not running all cores happily reach the C10 state.

I tried by just launching and stopping pipewire from the shell and I can consistently reproduce this behaviour.

Edited Mar 28, 2020 by Mathieu Velten
Assignee
Assign to
Time tracking