[HDA-Intel - HDA Intel, playback] Underruns, dropouts or crackling sound

Bug #1291616 reported by joe
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Description: Ubuntu 12.04.4 LTS
Release: 12.04

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.8.0-37.53~precise1-generic 3.8.13.18
Uname: Linux 3.8.0-37-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-37-generic.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC260 Analog [ALC260 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC260 Analog [ALC260 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: george 1811 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x80000000 irq 41'
   Mixer name : 'Realtek ALC260'
   Components : 'HDA:10ec0260,104d0000,00100300 HDA:14f12bfa,104d0200,00090000'
   Controls : 18
   Simple ctrls : 7
Date: Wed Mar 12 21:00:56 2014
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [HDA-Intel - HDA Intel, playback] Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/02/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R0084J1
dmi.chassis.asset.tag: Reserved
dmi.chassis.type: 10
dmi.chassis.vendor: Reserved
dmi.chassis.version: Reserved
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0084J1:bd06/02/2006:svnSonyCorporation:pnVGN-FS315M:pvrC3LLRJF8:cvnReserved:ct10:cvrReserved:
dmi.product.name: VGN-FS315M
dmi.product.version: C3LLRJF8
dmi.sys.vendor: Sony Corporation

Revision history for this message
joe (rachie-archie) wrote :
Revision history for this message
joe (rachie-archie) wrote :

hi i would be most grateful for any help on this issue, have tried running through alsa install but seeed to make no difference and on sound options there is nothing in output device list, sound is still there but with frequent pops. Thankyou ubuntu community, one love x

Revision history for this message
Raymond (superquad-vortex2) wrote :
Download full text (3.9 KiB)

0:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 03)
 Subsystem: Sony Corporation Device [104d:81bb]

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=d08c5ef2a039393eaf2ab2152db5f07790fa0f40

seem BIOS did not setup properly,

do your notebook support dock station or line out Jack ?

Node 0x0f [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Control: name="Headphone Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Headphone Jack", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0001003f: IN OUT HP EAPD Detect Trigger ImpSense
  EAPD 0x2: EAPD
  Pin Default 0x02014110: [Jack] Line Out at Ext Front
    Conn = 1/8, Color = Green
    DefAssociation = 0x1, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0xc0: OUT HP
  Unsolicited: tag=01, enabled=1
  Connection: 1
     0x08
Node 0x10 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Control: name="PCM Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Line Out Jack", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0001003f: IN OUT HP EAPD Detect Trigger ImpSense
  EAPD 0x2: EAPD
  Pin Default 0x21011120: [Jack] Line Out at Sep Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0x2, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=02, enabled=1
  Connection: 1
     0x09

Node 0x12 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Control: name="Mic Phantom Jack", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x80 0x80]
  Pincap 0x0000133f: IN OUT HP Detect Trigger ImpSense
    Vref caps: HIZ 50 80
  Pin Default 0x02a15910: [Jack] Mic at Ext Front
    Conn = 1/8, Color = Red
    DefAssociation = 0x1, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x21: IN VREF_50
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x0b
Node 0x13 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x80 0x80]
  Pincap 0x0000133f: IN OUT HP Detect Trigger ImpSense
    Vref caps: HIZ 50 80
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x20: IN VREF_HIZ
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x0c
Node 0x14 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x80 0x80]
  Pincap 0x0000133f: IN OUT HP Detect Trigger ImpSense
    Vref caps: HIZ 50 80
  Pin Default 0x21845120: [Jack] Line In at Sep Rear
    Conn = RCA, Color = Red
    DefAssociation = 0x2, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x20: IN VREF_HIZ
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x0d
Node 0x15 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x80 0x80]
  Pincap 0...

Read more...

Anders (eddiedog988)
Changed in alsa-driver (Ubuntu):
status: New → Confirmed
Revision history for this message
Raymond (superquad-vortex2) wrote :
Revision history for this message
joe (rachie-archie) wrote :

tried latest driver, some of the options in sound preferences have returned but no improvement in sound. how do i apply the patch? i do have jack out and docking station ability in laptop but dont use either. This problemjust began one day, sound was fine before, is there a way to repair the file registry or something, sorry im not very good with ubuntu yet. cheers, onelove x

Revision history for this message
Raymond (superquad-vortex2) wrote :

post the output of alsa-info.sh

https://wiki.ubuntu.com/Audio/AlsaInfo

00:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 03)
 Subsystem: Sony Corporation Device [104d:81bb]

your pci ssid same as the reporter 's ssid

+ SND_PCI_QUIRK(0x104d, 0x81bb, "Sony VAIO", ALC260_FIXUP_VAIO_PINS),

if you still have problems , you need to send email to the author and reporter about your case

Revision history for this message
Raymond (superquad-vortex2) wrote :

seem jack detection problem

try hint

trigger_sense=0

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/Documentation/sound/alsa/HD-Audio.txt

Mar 12 21:02:08 vortexwizard pulseaudio[1811]: ( 12.766| 3.379) [pulseaudio] module-alsa-card.c: Jack 'Headphone Jack' is now plugged in
Mar 12 21:02:08 vortexwizard pulseaudio[1811]: ( 12.779| 0.012) [pulseaudio] device-port.c: Setting port analog-output-headphones to status yes
Mar 12 21:02:08 vortexwizard pulseaudio[1811]: ( 12.779| 0.000) [pulseaudio] module-switch-on-port-available.c: finding port analog-output-headphones
Mar 12 21:02:08 vortexwizard pulseaudio[1811]: ( 12.792| 0.013) [pulseaudio] module-alsa-card.c: Jack 'Headphone Jack' is now unplugged
Mar 12 21:02:08 vortexwizard pulseaudio[1811]: ( 12.793| 0.000) [pulseaudio] device-port.c: Setting port analog-output-headphones to status no
Mar 12 21:02:08 vortexwizard pulseaudio[1811]: ( 12.793| 0.000) [pulseaudio] module-switch-on-port-available.c: finding port analog-output-headphones
Mar 12 21:02:09 vortexwizard pulseaudio[1811]: ( 13.059| 0.266) [pulseaudio] module-alsa-card.c: Jack 'Headphone Jack' is now plugged in
Mar 12 21:02:09 vortexwizard pulseaudio[1811]: ( 13.059| 0.000) [pulseaudio] device-port.c: Setting port analog-output-headphones to status yes
Mar 12 21:02:09 vortexwizard pulseaudio[1811]: ( 13.059| 0.000) [pulseaudio] module-switch-on-port-available.c: finding port analog-output-headphones
Mar 12 21:02:09 vortexwizard pulseaudio[1811]: ( 13.086| 0.026) [pulseaudio] module-alsa-card.c: Jack 'Headphone Jack' is now unplugged

Node 0x0f [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Control: name="Headphone Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Headphone Jack", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0001003f: IN OUT HP EAPD Detect Trigger ImpSense
  EAPD 0x2: EAPD
  Pin Default 0x02014110: [Jack] Line Out at Ext Front
    Conn = 1/8, Color = Green
    DefAssociation = 0x1, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0xc0: OUT HP
  Unsolicited: tag=01, enabled=1
  Connection: 1
     0x08

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "alc260_no_trigger_sense.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
joe (rachie-archie) wrote :

george@vortexwizard:~$ alsa-info.sh
alsa-info.sh: command not found
george@vortexwizard:~$ cd ~/
george@vortexwizard:~$ wget http://www.alsa-project.org/alsa-info.sh -O alsa-info.sh && bash alsa-info.sh
--2014-03-29 23:11:26-- http://www.alsa-project.org/alsa-info.sh
Resolving www.alsa-project.org (www.alsa-project.org)... 77.48.224.243
Connecting to www.alsa-project.org (www.alsa-project.org)|77.48.224.243|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;hb=refs/heads/build;f=alsa/utils/alsa-info.sh [following]
--2014-03-29 23:11:27-- http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;hb=refs/heads/build;f=alsa/utils/alsa-info.sh
Resolving git.alsa-project.org (git.alsa-project.org)... 77.48.224.243
Connecting to git.alsa-project.org (git.alsa-project.org)|77.48.224.243|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-sh]
Saving to: `alsa-info.sh'

    [ <=> ] 27,678 --.-K/s in 0.1s

2014-03-29 23:11:28 (206 KB/s) - `alsa-info.sh' saved [27678]

ALSA Information Script v 0.4.63
--------------------------------

This script visits the following commands/files to collect diagnostic
information about your ALSA installation and sound related hardware.

  dmesg
  lspci
  lsmod
  aplay
  amixer
  alsactl
  /proc/asound/
  /sys/class/sound/
  ~/.asoundrc (etc.)

See 'alsa-info.sh --help' for command line options.

Automatically upload ALSA information to www.alsa-project.org? [y/N] :

Revision history for this message
joe (rachie-archie) wrote :

raymond, what do you mean by your last post, i dont follow? is there something in there you think i should do?

Revision history for this message
Raymond (superquad-vortex2) wrote :

you need to find out whether the problem is fixed by using early patching to disable trigger sense

Early Patching
~~~~~~~~~~~~~~
When CONFIG_SND_HDA_PATCH_LOADER=y is set, you can pass a "patch" as a
firmware file for modifying the HD-audio setup before initializing the
codec. This can work basically like the reconfiguration via sysfs in
the above, but it does it before the first codec configuration.

A patch file is a plain text file which looks like below:

------------------------------------------------------------------------
  [codec]
  0x12345678 0xabcd1234 2

  [hint]
  trigger_sense=0
------------------------------------------------------------------------

The file needs to have a line `[codec]`. The next line should contain
three numbers indicating the codec vendor-id (0x12345678 in the
example), the codec subsystem-id (0xabcd1234) and the address (2) of
the codec. The rest patch entries are applied to this specified codec
until another codec entry is given. Passing 0 or a negative number to
the first or the second value will make the check of the corresponding
field be skipped. It'll be useful for really broken devices that don't
initialize SSID properly.

The hd-audio driver reads the file via request_firmware(). Thus,
a patch file has to be located on the appropriate firmware path,
typically, /lib/firmware. For example, when you pass the option
`patch=hda-init.fw`, the file /lib/firmware/hda-init.fw must be
present.

The patch module option is specific to each card instance, and you
need to give one file name for each instance, separated by commas.
For example, if you have two cards, one for an on-board analog and one
for an HDMI video board, you may pass patch option like below:
------------------------------------------------------------------------
    options snd-hda-intel patch=on-board-patch,hdmi-patch
------------------------------------------------------------------------

Revision history for this message
Raymond (superquad-vortex2) wrote :

if the problem is still not fixed

you need to enable trace points to trace the hda_unsol_event which is triggered when you plug and unplug any jack

Tracepoints
~~~~~~~~~~~
The hd-audio driver gives a few basic tracepoints.
`hda:hda_send_cmd` traces each CORB write while `hda:hda_get_response`
traces the response from RIRB (only when read from the codec driver).
`hda:hda_bus_reset` traces the bus-reset due to fatal error, etc,
`hda:hda_unsol_event` traces the unsolicited events, and
`hda:hda_power_down` and `hda:hda_power_up` trace the power down/up
via power-saving behavior.

Enabling all tracepoints can be done like
------------------------------------------------------------------------
  # echo 1 > /sys/kernel/debug/tracing/events/hda/enable
------------------------------------------------------------------------
then after some commands, you can traces from
/sys/kernel/debug/tracing/trace file. For example, when you want to
trace what codec command is sent, enable the tracepoint like:
------------------------------------------------------------------------
  # cat /sys/kernel/debug/tracing/trace
  # tracer: nop
  #
  # TASK-PID CPU# TIMESTAMP FUNCTION
  # | | | | |
         <...>-7807 [002] 105147.774889: hda_send_cmd: [0:0] val=e3a019
         <...>-7807 [002] 105147.774893: hda_send_cmd: [0:0] val=e39019
         <...>-7807 [002] 105147.999542: hda_send_cmd: [0:0] val=e3a01a
         <...>-7807 [002] 105147.999543: hda_send_cmd: [0:0] val=e3901a
         <...>-26764 [001] 349222.837143: hda_send_cmd: [0:0] val=e3a019
         <...>-26764 [001] 349222.837148: hda_send_cmd: [0:0] val=e39019
         <...>-26764 [001] 349223.058539: hda_send_cmd: [0:0] val=e3a01a
         <...>-26764 [001] 349223.058541: hda_send_cmd: [0:0] val=e3901a

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in alsa-driver (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]

Changed in alsa-driver (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.