Bug 1831736

Summary: Keeping the sequencer device open block going into C10 sleep state
Product: [Fedora] Fedora Reporter: Wim Taymans <wtaymans>
Component: pipewireAssignee: Wim Taymans <wtaymans>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: brunovern.a, jkysela, wtaymans
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pipewire-0.3.5-1.fc32 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-14 02:36:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Wim Taymans 2020-05-05 14:32:18 UTC
PipeWire tries to transparently map all midi ports to PipeWire ports (like JACK) but for that it needs to be able to monitor the sequencer events. It does not keep the hardware devices open by subscribing to the ports unless needed.

This is the output of acconnect -l on my machine:

client 0: 'System' [type=kernel]
    0 'Timer           '
	Connecting To: 128:0[real:0]
    1 'Announce        '
	Connecting To: 128:0[real:0]
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 16: 'UMC404HD 192k' [type=kernel,card=0]
    0 'UMC404HD 192k MIDI 1'
client 24: 'WORLDE easy control' [type=kernel,card=2]
    0 'WORLDE easy control MIDI 1'
client 128: 'PipeWire-System' [type=user,pid=32097]
    0 'input           '
	Connected From: 0:1[real:0], 0:0[real:0]
client 129: 'PipeWire-RT-Event' [type=user,pid=32097]
    0 'input           '

In this state, we 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 closing the sequencer, all cores happily reach the C10 state again.

Is there a reason for blocking deep sleep states when the sequencer is open? is this something that can be fixed in the driver?

Comment 1 Wim Taymans 2020-05-11 13:39:24 UTC
It was the queue used for the announce messages that uses a timer. Removing the queue resolved issue.

Comment 2 Fedora Update System 2020-05-11 13:40:06 UTC
FEDORA-2020-736fbfee04 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-736fbfee04

Comment 3 Fedora Update System 2020-05-12 07:18:53 UTC
FEDORA-2020-736fbfee04 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-736fbfee04`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-736fbfee04

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2020-05-14 02:36:00 UTC
FEDORA-2020-736fbfee04 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.