Bug 901929
| Summary: | Speakers sputter/stutter when PulseAudio is running | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Marc Santoro <msantoro> | ||||
| Component: | alsa-lib | Assignee: | Lennart Poettering <lpoetter> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | brendan.jones.it, jkysela, lkundrak, lpoetter, rdieter, superquad.vortex2 | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-02-05 15:21:56 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: | |||||||
| Attachments: |
|
||||||
|
Description
Marc Santoro
2013-01-20 01:43:30 UTC
post the output of alsa-info.sh I: [alsa-sink] alsa-sink.c: Hardware volume ranges from -181.50 dB to 0.00 dB. check whether your realtek codec really have dB range from -181.5 to 0dB Created attachment 685546 [details]
alsa-info output
alsa-info attached. Not sure how to check the real volume range? (Also, confirmed the issue doesn't happen on this computer in Windows 8) state.PCH {
control.1 {
iface MIXER
name 'Front Playback Volume'
value.0 87
value.1 87
comment {
access 'read write'
type INTEGER
count 2
range '0 - 87'
dbmin -6525
dbmax 0
dbvalue.0 0
dbvalue.1 0
}
}
min dB is -65.25 and Max dB is zero
number of steps 0x57
Node 0x0c [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
Control: name="Front Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-In vals: [0x00 0x00] [0x00 0x00]
Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0
Amp-Out vals: [0x3d 0x3d]
Connection: 2
0x02 0x0b
what is the dB range of 24 bits audio ?
Node 0x02 [Audio Output] wcaps 0x411: Stereo
Device: name="ALC898 Analog", type="Audio", device=0
Converter: stream=8, channel=0
PCM:
rates [0x5e0]: 44100 48000 88200 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Power states: D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
I accidentally lied: this does happen with only ALSA. It's been happening for the past 20 minutes with pulseaudio disabled (via killall and .pulse/client.conf), running rhythmbox in an otherwise default configuration. It seems like maybe I just need something accessing the audio device (i.e., pulseaudio does when I first log in until it idles out, which makes it seem like the culprit, but killing pulseaudio stops it until I run another application which uses ALSA?) I'll go ahead and reassign this against ALSA. Ok, no alsa-core package? Should this be against kernel then? Loaded sound module options
!!--------------------------
!!Module: snd_hda_intel
power_save : 0
power_save_controller : Y
try turn off power save controller
[root@tau parameters]# echo N > /sys/module/snd_hda_intel/parameters/power_save_controller [root@tau parameters]# cat power_save_controller N Like that? (I'll let you know what happens) Sadly, no change to report - sputter remains! This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |