Bug 901929 - Speakers sputter/stutter when PulseAudio is running
Summary: Speakers sputter/stutter when PulseAudio is running
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-lib
Version: 18
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-20 01:43 UTC by Marc Santoro
Modified: 2014-02-05 15:21 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 15:21:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
alsa-info output (57.45 KB, text/plain)
2013-01-23 00:51 UTC, Marc Santoro
no flags Details

Description Marc Santoro 2013-01-20 01:43:30 UTC
Description of problem: Apparent symptoms are that speakers emit clicking noise when audio is not playing, and stutter when audio is playing. Does not matter whether audio is playing. Happens once every few (5-15) minutes.


Version-Release number of selected component (if applicable):

(rpm -qa | grep pulseaudio)
pulseaudio-libs-2.1-5.fc18.x86_64
pulseaudio-libs-2.1-5.fc18.i686
pulseaudio-libs-glib2-2.1-5.fc18.x86_64
pulseaudio-gdm-hooks-2.1-5.fc18.x86_64
pulseaudio-utils-2.1-5.fc18.x86_64
pulseaudio-module-bluetooth-2.1-5.fc18.x86_64
pulseaudio-2.1-5.fc18.x86_64
(uname -a)
Linux tau 3.7.2-201.fc18.x86_64 #1 SMP Fri Jan 11 22:16:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
(lspci | grep Audio)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
(dmesg | grep -i alsa)
[   19.732451] ALSA sound/pci/hda/patch_realtek.c:1241 SKU: Nid=0x1d sku_cfg=0x4007e619
[   19.732453] ALSA sound/pci/hda/patch_realtek.c:1243 SKU: port_connectivity=0x1
[   19.732454] ALSA sound/pci/hda/patch_realtek.c:1244 SKU: enable_pcbeep=0x0
[   19.732456] ALSA sound/pci/hda/patch_realtek.c:1245 SKU: check_sum=0x00000007
[   19.732457] ALSA sound/pci/hda/patch_realtek.c:1246 SKU: customization=0x000000e6
[   19.732458] ALSA sound/pci/hda/patch_realtek.c:1247 SKU: external_amp=0x3
[   19.732459] ALSA sound/pci/hda/patch_realtek.c:1248 SKU: platform_type=0x0
[   19.732460] ALSA sound/pci/hda/patch_realtek.c:1249 SKU: swap=0x0
[   19.732461] ALSA sound/pci/hda/patch_realtek.c:1250 SKU: override=0x1
[   19.732464] ALSA sound/pci/hda/hda_auto_parser.c:318 autoconfig: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
[   19.732465] ALSA sound/pci/hda/hda_auto_parser.c:322    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   19.732467] ALSA sound/pci/hda/hda_auto_parser.c:326    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[   19.732468] ALSA sound/pci/hda/hda_auto_parser.c:327    mono: mono_out=0x0
[   19.732469] ALSA sound/pci/hda/hda_auto_parser.c:330    dig-out=0x11/0x1e
[   19.732470] ALSA sound/pci/hda/hda_auto_parser.c:331    inputs:
[   19.732471] ALSA sound/pci/hda/hda_auto_parser.c:335      Rear Mic=0x18
[   19.732473] ALSA sound/pci/hda/hda_auto_parser.c:335      Front Mic=0x19
[   19.732474] ALSA sound/pci/hda/hda_auto_parser.c:335      Line=0x1a
[   19.735200] ALSA sound/pci/hda/patch_realtek.c:1304 realtek: No valid SSID, checking pincfg 0x4007e619 for NID 0x1d
[   19.735201] ALSA sound/pci/hda/patch_realtek.c:1320 realtek: Enabling init ASM_ID=0xe619 CODEC_ID=10ec0899
[   19.749133] ALSA sound/pci/hda/hda_intel.c:2698 0000:01:00.1: Handle VGA-switcheroo audio client
[   19.760707] ALSA sound/pci/hda/hda_intel.c:1625 Enable delay in RIRB handling


How reproducible:
Happens intermittently once I've logged into X (KDE or Gnome). 

Additional info:
Running pulseaudio -v:
I: [alsa-sink] alsa-sink.c: Successfully enabled deferred volume.
I: [alsa-sink] alsa-sink.c: Hardware volume ranges from -181.50 dB to 0.00 dB.
I: [alsa-sink] alsa-sink.c: Fixing base volume to 0.00 dB
I: [alsa-sink] alsa-sink.c: Using hardware volume control. Hardware dB scale supported.
I: [alsa-sink] alsa-sink.c: Using hardware mute control.
I: [pulseaudio] sink.c: Changed port of sink 1 "alsa_output.pci-0000_00_1b.0.analog-stereo" to analog-output-headphones
I: [pulseaudio] module-device-restore.c: Restoring volume for sink alsa_output.pci-0000_00_1b.0.analog-stereo.
I: [alsa-sink] alsa-sink.c: Successfully enabled deferred volume.
I: [alsa-sink] alsa-sink.c: Hardware volume ranges from -181.50 dB to 0.00 dB.
I: [alsa-sink] alsa-sink.c: Fixing base volume to 0.00 dB
I: [alsa-sink] alsa-sink.c: Using hardware volume control. Hardware dB scale supported.
I: [alsa-sink] alsa-sink.c: Using hardware mute control.
I: [pulseaudio] sink.c: Changed port of sink 1 "alsa_output.pci-0000_00_1b.0.analog-stereo" to analog-output
I: [pulseaudio] module-device-restore.c: Restoring volume for sink alsa_output.pci-0000_00_1b.0.analog-stereo.

It seems like PulseAudio/alsa-sink is incorrectly detecting a headphone being plugged in and then removed - no headphone has been plugged in. I'm reporting this against PulseAudio instead of ALSA because, with PulseAudio disabled, audio plays normally and there is no sputtering.

Comment 1 Raymond 2013-01-20 14:47:29 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

Comment 2 Marc Santoro 2013-01-23 00:51:10 UTC
Created attachment 685546 [details]
alsa-info output

Comment 3 Marc Santoro 2013-01-23 00:54:58 UTC
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)

Comment 4 Raymond 2013-01-23 01:11:50 UTC
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

Comment 5 Raymond 2013-01-23 01:25:28 UTC
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

Comment 6 Marc Santoro 2013-01-23 03:22:08 UTC
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.

Comment 7 Marc Santoro 2013-01-23 03:24:09 UTC
Ok, no alsa-core package? Should this be against kernel then?

Comment 8 Raymond 2013-01-23 03:32:14 UTC
	 Loaded sound module options
!!--------------------------

!!Module: snd_hda_intel



    power_save : 0
	power_save_controller : Y

try turn off power save controller

Comment 9 Marc Santoro 2013-01-23 03:40:23 UTC
[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)

Comment 10 Marc Santoro 2013-01-23 03:48:17 UTC
Sadly, no change to report - sputter remains!

Comment 11 Fedora End Of Life 2013-12-21 10:35:24 UTC
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.

Comment 12 Fedora End Of Life 2014-02-05 15:21:59 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.