[INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable

Bug #1201528 reported by Natalia Bidart
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Confirmed
Medium
Unassigned
Nominated for Xenial by Natalia Bidart
Vivid
Confirmed
Medium
Unassigned
linux (Ubuntu)
Confirmed
Medium
Unassigned
Nominated for Xenial by Natalia Bidart
Vivid
Won't Fix
Medium
Unassigned

Bug Description

This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well.

The symptom is:

* after some period of sound usage, playback stops working

What I mean with sound usage is:

I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine).

The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nessita 2627 F.... pulseaudio
Date: Mon Jul 15 14:40:20 2013
InstallationDate: Installed on 2011-12-20 (572 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
Symptom_AlsaPlaybackTestStderr:
 W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r
  x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r
  T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: None of the above
Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem
UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago)
dmi.bios.date: 08/05/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP55WG
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE57269-404
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr:
---
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nessita 13188 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=bd987ac2-eb4b-43e7-881b-4cf2b5078e4b
InstallationDate: Installed on 2014-05-11 (366 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e91bd3a4-787b-404b-9f19-aa6dcbe707b0 ro quiet splash
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-16-generic N/A
 linux-backports-modules-3.19.0-16-generic N/A
 linux-firmware 1.143
RfKill:

Tags: vivid vivid vivid vivid
Uname: Linux 3.19.0-16-generic x86_64
UpgradeStatus: Upgraded to vivid on 2015-03-11 (61 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/05/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP55WG
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE57269-404
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr:

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
summary: - [, Realtek ALC889, Green Headphone Out, Front] Playback problem
+ [Realtek ALC889] - Audio Playback Unavailable
Revision history for this message
Natalia Bidart (nataliabidart) wrote : Re: [Realtek ALC889] - Audio Playback Unavailable

Tested latest kernel available:

linux-image-3.8.13-03081304-generic_3.8.13-03081304.201307032035_amd64.deb

Installed, rebooted in the new kernel, opened skype, make a test call (all good, as before), called someone and got the same audio playback dying issue.

Revision history for this message
Luke Yelavich (themuso) wrote : Re: [Bug 1201528] Re: [Realtek ALC889] - Audio Playback Unavailable

Please try to get a log from PulseAudio when this happens, see https://wiki.ubuntu.com/PulseAudio/Log for instructions on how to do this.

Revision history for this message
Natalia Bidart (nataliabidart) wrote : Re: [Realtek ALC889] - Audio Playback Unavailable

Attached verbose log during reproduction of the issue as requested by Luke.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Revision history for this message
Natalia Bidart (nataliabidart) wrote :

I also tested a clean raring by booting it in mem from a pendrive. I managed to reproduce the same unwanted effect by using google hangouts and tweaking sound levels from the "Sound settings" app below the sound icon in the systray.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

As per the advice from #ubuntu-kernel, following https://wiki.ubuntu.com/Audio/PositionReporting, seems like setting options snd-hda-intel position_fix=2 did the trick for me. Will re-open if audio breaks again.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Update: after using this setup (position_fix=2) for a while, audio broke again, not sure when or how.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Following instructions from https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS:

nessita@dali:~$ sudo dpkg -i oem-audio-hda-daily-dkms_0.201307180559~raring1_all.deb
Selecting previously unselected package oem-audio-hda-daily-dkms.
(Reading database ... 277693 files and directories currently installed.)
Unpacking oem-audio-hda-daily-dkms (from oem-audio-hda-daily-dkms_0.201307180559~raring1_all.deb) ...
Setting up oem-audio-hda-daily-dkms (0.201307180559~raring1) ...
Loading new oem-audio-hda-daily-0.201307180559~raring1 DKMS files...
First Installation: checking all kernels...
Building only for 3.8.0-26-generic
Building for architecture x86_64
Building initial module for 3.8.0-26-generic
Done.

snd-hda-codec-via:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-codec-si3054.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-codec-ca0110.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-codec-ca0132.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-codec-analog.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-codec-realtek.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-codec.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-codec-conexant.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-codec-hdmi.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-intel.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-codec-idt.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-codec-cirrus.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

snd-hda-codec-cmedia.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/3.8.0-26-generic/updates/dkms/

depmod........

DKMS: install completed.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Download full text (17.7 KiB)

The update to dkms did not help. A piece of output from pulseaudio, once audio playback is broken, when playing a video with mplayer:

# tail -f /var/log/syslog
Jul 19 12:45:34 pulseaudio[4457]: last message repeated 10 times
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] client.c: Created 4 "Native client (UNIX socket client)"
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] protocol-native.c: Protocol version: remote 27, local 27
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] protocol-native.c: SHM possible: yes
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] protocol-native.c: Negotiated SHM: yes
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] module-augment-properties.c: Looking for .desktop file for mplayer
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] module-stream-restore.c: Restoring device for stream sink-input-by-application-name:MPlayer.
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] module-intended-roles.c: Not setting device for stream audio stream, because already set.
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] sink-input.c: Trying to change sample rate
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] sink.c: Cannot update rate, monitor source is RUNNING
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] module-stream-restore.c: Restoring volume for sink input sink-input-by-application-name:MPlayer.
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] module-stream-restore.c: Restoring mute state for sink input sink-input-by-application-name:MPlayer.
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-0000_00_1b.0.analog-stereo becomes busy.
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] resampler.c: Using resampler 'speex-float-1'
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] resampler.c: Using float32le as working format.
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] resampler.c: Choosing speex quality setting 1.
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] memblockq.c: memblockq requested: maxlength=33554432, tlength=0, base=4, prebuf=0, minreq=1 maxrewind=0
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] memblockq.c: memblockq sanitized: maxlength=33554432, tlength=33554432, base=4, prebuf=0, minreq=4 maxrewind=0
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] sink-input.c: Created input 1 "audio stream" on alsa_output.pci-0000_00_1b.0.analog-stereo with sample spec float32le 2ch 48000Hz and channel map front-left,front-right
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] sink-input.c: media.name = "audio stream"
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] sink-input.c: application.name = "MPlayer"
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] sink-input.c: native-protocol.peer = "UNIX socket client"
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] sink-input.c: native-protocol.version = "27"
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] sink-input.c: application.process.id = "4466"
Jul 19 12:45:34 dali pulseaudio[4457]: [pulseaudio] sink-inp...

Revision history for this message
David Henningsson (diwic) wrote :

After some debugging on IRC, I'm still not sure what's causing the problem. We should try a build with DEBUG_TIMING (in module-alsa-sink.c) on for even more verbose logging in PulseAudio.

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

do your computer chassis have hda front audio panel with Jack detection ?

do your BIOS have any option to set front audio panel type :hda or AC97 ?

MISC = NO_PRESENCE mean front audio panel has no Jack detection circuit

http://www.intel.com/support/motherboards/desktop/sb/cs-015851.htm

control.45 {
  iface CARD
  name 'Front Headphone Phantom Jack'
  value true
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
 control.46 {
  iface CARD
  name 'Front Mic Phantom Jack'
  value true
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }

Node 0x15 [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="Front Headphone Phantom Jack", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0000003c: IN OUT HP Detect
  Pin Default 0x02214520: [Jack] HP Out at Ext Front
    Conn = 1/8, Color = Green
    DefAssociation = 0x2, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0xc0: OUT HP
  Unsolicited: tag=00, enabled=0
  Connection: 5
     0x0c 0x0d 0x0e 0x0f 0x26*

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Raymond, below some answers:

* do your computer chassis have hda front audio panel with Jack detection ?

The computer chassis does have front audio panel, I'm not sure how to check "visually" if it has Jack detection or not. The chassis is exactly this one: http://www.sentey.com/en_productos_details.php?tipo=Gabinetes&ctg=Professional%20Series&prod=ps2-3270

* do your BIOS have any option to set front audio panel type :hda or AC97?

Will check next time I reboot; motherboard is Intel DP55WG (perhaps that answers your question?)

In any case, is worth noting that audio playback works perfectly both in the headset using the front audio connectot and in the speakers plugged in the rear audio output (they work perfectly *at the same time*, until they both stop working altogether).
I have also tried unplugging one of each at a time (ie have only headset, have only speakers). This does not look like a hardware issue, since audio works for some random amount of time after a reboot.

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

you can use hda-jack-sense-test to find out whether the front audio panel headphone and mic have Jack detection or not ?

it is strange that dB min and dBmax of virtual master is different from it slaves (e.g. front, suroound, center, pre and headphone)

state.MID {
 control.1 {
  iface MIXER
  name 'Front Playback Volume'
  value.0 62
  value.1 62
  comment {
   access 'read write'
   type INTEGER
   count 2
   range '0 - 64'
   dbmin -6200
   dbmax 200
   dbvalue.0 0
   dbvalue.1 0
  }
 }

control.39 {
  iface MIXER
  name 'Master Playback Volume'
  value 60
  comment {
   access 'read write'
   type INTEGER
   count 1
   range '0 - 64'
   dbmin -6400
   dbmax 0
   dbvalue.0 -400
  }
 }

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

nessita@dali:~$ sudo hda-jack-sense-test
Traceback (most recent call last):
  File "/usr/bin/hda-jack-sense-test", line 47, in <module>
    codec = HDACodec(cardindex, codecindex)
  File "/usr/share/snd-hda-tools/hda_codec.py", line 1023, in __init__
    self.fd = os.open("/dev/snd/hwC%sD%s" % (card, device), os.O_RDWR)
OSError: [Errno 2] No such file or directory: '/dev/snd/hwC0D0'

nessita@dali:~$ ls /dev/snd/
by-path/ controlC0 hwC0D2 pcmC0D0c pcmC0D0p pcmC0D1c pcmC0D1p pcmC0D2c seq timer

Edited the tool so /dev/snd/hwC0D2 was used and got:

nessita@dali:~$ sudo hda-jack-sense-test
Unable to find proc file '/proc/asound/card0/codec#0'
Pin 0x14 (Green Line Out): present = No
Pin 0x16 (Orange Line Out): present = No
Pin 0x17 (Grey Line Out): present = No
Pin 0x19 (Black Line Out): present = Yes
Pin 0x1a (Blue Line In): present = No
Pin 0x1b (Pink Mic): present = No

At the time the test was run, I had the speakers connected to the black line out, and the headset in the front panel. Audio playback is not working at the time the test was run.

Still need to check the BIOS setting, need to reboot to do that, will try to get that done today.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Rebooted and checked the BIOS. Couldn't find something specifically related to the options AC97 or :hda, but took a screenshot of the peripheral devices screen (shows "Legacy Front Panel Audio -> <enabled>":

http://ubuntuone.com/3y5DR6FKZdWS3WKU1GgQ73

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

you may need to disable Legacy front audio panel in BIOS setup

 check whether misc bit is clear in node 0x15 and 0x18

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

the availablityy of headphone should be either yes or no instead of unknown

ports:
  analog-output: Analog Output (priority 9900, latency offset 0 usec, available: unknown)
   properties:

  analog-output-headphones: Headphones (priority 9000, latency offset 0 usec, available: unknown)
   properties:
    device.icon_name = "audio-headphones"
 active port: <analog-output>
2 source(s) available.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Raymond:

Re: "you may need to disable Legacy front audio panel in BIOS setup" -> does this mean I will not be able to use the headset from the front panel?

Re: "check whether misc bit is clear in node 0x15 and 0x18" -> no idea how to do this, would you please advice what do I need to do?

And is the comment #18 for me is it technical info for the bug report? If the former, I'm not sure what that means either.

Thanks!

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

leagcy front audio panel is AC97 AUDIO PANEL without Jack detection

you have to disable it to use HDA front audio panel with Jack detection

the rear panel jacks are auto muted when you plugged the headphone by the driver

the codec info is in the output of alsa-info.sh

the headphone won`t be available in sound preference since BIOS set misc bit of pin default of front panel jacks for AC97 audio panel

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

control.41 {
  iface CARD
  name 'Line Out Front Jack'
  value true
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
 control.42 {
  iface CARD
  name 'Line Out Surround Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
 control.43 {
  iface CARD
  name 'Line Out CLFE Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
 control.44 {
  iface CARD
  name 'Line Out Side Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }

 control.47 {
  iface CARD
  name 'Rear Mic Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
 control.48 {
  iface CARD
  name 'Line Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }

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

you have to ask the author since he assume no gain in vmaster but slaves can have gain in your case

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

+/*
+ * Add a slave control to the group with the given master control
+ *
+ * All slaves must be the same type (returning the same information
+ * via info callback). The fucntion doesn't check it, so it's your
+ * responsibility.
+ *
+ * Also, some additional limitations:
+ * - at most two channels
+ * - logarithmic volume control (dB level), no linear volume
+ * - master can only attenuate the volume, no gain

Revision history for this message
David Henningsson (diwic) wrote :

While it would be interesting to see if jack detection works differently if "Legacy Front Panel Audio" was disabled, it is unrelated to this issue.

This issue is about when sound suddenly stops to work, and does so for all output jacks.

Revision history for this message
David Henningsson (diwic) wrote :

One thing to check is what's causing the > 10 ms system latencies here. In a root shell, execute this command:

cd /sys/kernel/debug/tracing
echo wakeup_rt > current_tracer
echo 1 > tracing_on

Run for a minute or two, then

cat trace > /tmp/trace.txt
echo 0 > tracing on

Then attach /tmp/trace.txt here. Thanks!

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Revision history for this message
David Henningsson (diwic) wrote :

Hi,

I've made a special build in this PPA:

https://launchpad.net/~diwic/+archive/pulse-timing-test

Once it has finished building, could you try to give me a pulseaudio verbose log? Try to reproduce the hangout/mumble/skype bug with the pulseaudio package in this ppa, and the log enabled. Thanks!

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

> sudo hda-jack-sense-test
Unable to find proc file '/proc/asound/card0/codec#0'
Pin 0x14 (Green Line Out): present = No
Pin 0x16 (Orange Line Out): present = No
Pin 0x17 (Grey Line Out): present = No
Pin 0x19 (Black Line Out): present = Yes
Pin 0x1a (Blue Line In): present = No
Pin 0x1b (Pink Mic): present = No

If the objective of hda-jack-sense-test is to figure out if your BIOS is lying to you
about what pin is used for what.

it should check those pin complex which pincap support DETECT instead of ignoring those Misc = NO_PRESENCE in order to find out whether the jack support jack sense or not

AC_PINCAP_PRES_DETECT (1<<2) /* presence detect capable */

Node 0x15 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Pincap 0x0000003c: IN OUT HP Detect
  Pin Default 0x02214520: [Jack] HP Out at Ext Front

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Revision history for this message
Natalia Bidart (nataliabidart) wrote :

nessita@dali:~$ apt-cache policy pulseaudio
pulseaudio:
  Installed: 1:4.0-0ubuntu1+debugtiming
  Candidate: 1:4.0-0ubuntu1+debugtiming
  Version table:
 *** 1:4.0-0ubuntu1+debugtiming 0
        500 http://ppa.launchpad.net/diwic/pulse-timing-test/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status
     1:3.0-0ubuntu6 0
        500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Removed verbose log to syslog and tried again with local verbose log as per wiki instrucions. Booted computer, logged in, ran pulseaudio, and opened mumble. Got this:

nessita@dali:~$ LANG=C pulseaudio -vvvv --log-time=1 > ~/pulseverbose.log 2>&1
Trace/breakpoint trap (core dumped)

Attaching verbose.log.

Ran pulseaudio with gdb, got:

Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 0x7fffed380700 (LWP 3580)]
0x00007fffedbad451 in ?? () from /usr/lib/pulse-4.0/modules/libalsa-util.so
(gdb) w
Ambiguous command "w": watch, wh, whatis, where, while, while-stepping, winheight, ws.
(gdb) where
#0 0x00007fffedbad451 in ?? () from /usr/lib/pulse-4.0/modules/libalsa-util.so
#1 0x00007fffedbaf164 in ?? () from /usr/lib/pulse-4.0/modules/libalsa-util.so
#2 0x00007ffff792bd63 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
#3 0x00007ffff6e34f8e in start_thread (arg=0x7fffed380700) at pthread_create.c:311
#4 0x00007ffff644de1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
(gdb)

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Installed updated pulseaudio from PPA and re-tested with:

LANG=C pulseaudio -vvvv --log-time=1 > ~/pulseverbose.log 2>&1

Got no crashes, but no audio playback either (mix did work this time). The pulseaudio log is 84M, so uploading it compressed with bzip2.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Revision history for this message
David Henningsson (diwic) wrote :

Looking at the latest logs, there are terrible delays, probably for which we cannot blame the graphics driver.

( 61.711| 0.007) D: [alsa-sink-ALC889 Analog] alsa-sink.c: Expected sleep: 9.27ms, real sleep: 7.91ms (diff -1.36 ms)
( 61.920| 0.204) D: [alsa-sink-ALC889 Analog] alsa-sink.c: Loop
( 61.920| 0.000) D: [alsa-sink-ALC889 Analog] alsa-sink.c: Buffer time: 46 ms; Sleep time: 10 ms; Process time: 35 ms
( 61.716| 0.005) D: [alsa-source-ALC889 Analog] alsa-source.c: Expected sleep: 19.99ms, real sleep: 20.09ms (diff 0.10 ms)
( 61.920| 0.000) D: [alsa-sink-ALC889 Analog] alsa-sink.c: avail: 95888
( 61.921| 0.000) D: [alsa-source-ALC889 Analog] alsa-source.c: Loop
( 61.921| 0.000) I: [alsa-sink-ALC889 Analog] alsa-sink.c: Underrun!

There is 200 ms of delay between the "Expected sleep" line and "Loop" line, which is not normal. Any chance you can look at the system as a whole to see what's causing these delays? I'm not really sure how to do this, but maybe "top" could give an initial indication if there's anything that's taking a lot of CPU power.

Revision history for this message
David Henningsson (diwic) wrote :

To sum up our IRC discussions, a few things to try are:

 - Install precise, verify it's still working correctly
 - Upgrade to a raring kernel in precise (install linux-generic-lts-raring-eol-upgrade and reboot) and see if this causes the problem to appear
 - If not, also upgrade to raring X stack in precise (install xserver-xorg-lts-raring and libgl1-mesa-glx-lts-raring, reboot) and see if this causes the problem to appear

Also, does anything appear in dmesg when these problems appear, that could give us a hint of what is happening?

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Download full text (3.2 KiB)

Booted in the raring PC with the audio issues. dmesg output before reproducing the issue has the following line that looks suspicious to me:

[13828.248950] hrtimer: interrupt took 15288 ns

When started pulseaudio with the -vvvv option dmesg showed (did not open any audio program yet):

[27622.091908] hda-intel 0000:00:1b.0: Unstable LPIB (65536 >= 8192); disabling LPIB delay counting

After reproducing the issue by using mumble, dmesg shows *nothing* new.
At this stage, top shows:

nessita@dali:~$ top

top - 15:50:13 up 7:45, 8 users, load average: 0.14, 0.22, 0.23
Tasks: 289 total, 3 running, 284 sleeping, 0 stopped, 2 zombie
%Cpu(s): 2.0 us, 1.6 sy, 0.0 ni, 95.9 id, 0.0 wa, 0.0 hi, 0.5 si, 0.0 st
KiB Mem: 8167864 total, 3780108 used, 4387756 free, 377504 buffers
KiB Swap: 6290428 total, 0 used, 6290428 free, 866680 cached

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
11852 nessita 20 0 1461m 55m 32m S 5.3 0.7 0:13.38 mumble
10633 nessita 9 -11 330m 7100 4364 R 2.3 0.1 0:05.73 pulseaudio

Last few lines from pulse log are:

.... a lot ....
( 168.054| 0.000) E: [alsa-sink-ALC889 Analog] protocol-native.c: request_bytes(192)
( 168.054| 0.000) E: [alsa-sink-ALC889 Analog] protocol-native.c: ALSA Playback, pop(): 0
( 168.054| 0.000) E: [pulseaudio] protocol-native.c: Requesting 2048 bytes
( 168.054| 0.000) E: [pulseaudio] protocol-native.c: signalling underflow
( 168.059| 0.004) E: [alsa-sink-ALC889 Analog] protocol-native.c: ALSA Playback, pop(): 0
( 169.389| 1.330) I: [alsa-sink-ALC889 Analog] alsa-sink.c: Scheduling delay of 1.02ms > 0.96ms, you might want to investigate this to improve latency...
( 173.060| 3.671) I: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-0000_00_1b.0.analog-stereo idle for too long, suspending ...
( 173.061| 0.000) I: [alsa-sink-ALC889 Analog] alsa-sink.c: Device suspended...
( 251.342| 78.281) I: [alsa-source-ALC889 Analog] alsa-source.c: Scheduling delay of 4.75ms, you might want to investigate this to improve latency...
( 251.409| 0.066) I: [alsa-source-ALC889 Analog] alsa-source.c: Scheduling delay of 12.15ms, you might want to investigate this to improve latency...
( 251.409| 0.000) I: [alsa-source-ALC889 Analog] alsa-source.c: Overrun!
( 251.409| 0.000) I: [alsa-source-ALC889 Analog] alsa-source.c: Increasing wakeup watermark to 16.00 ms
( 256.575| 5.166) I: [alsa-source-ALC889 Analog] alsa-source.c: Scheduling delay of 6.29ms, you might want to investigate this to improve latency...
( 256.591| 0.015) I: [alsa-source-ALC889 Analog] alsa-source.c: Scheduling delay of 5.32ms, you might want to investigate this to improve latency...
( 269.375| 12.784) I: [alsa-source-ALC889 Analog] alsa-source.c: Scheduling delay of 9.03ms, you might want to investigate this to improve latency...
( 277.341| 7.966) I: [alsa-source-ALC889 Analog] alsa-source.c: Scheduling delay of 6.62ms, you might want to investigate this to improve latency...
( 285.666| 8.324) I: [alsa-source-ALC889 Analog] alsa-source.c: ...

Read more...

Revision history for this message
David Henningsson (diwic) wrote :

> dmesg output before reproducing the issue has the following line that looks suspicious to me:
> [13828.248950] hrtimer: interrupt took 15288 ns

It seems a bit suspicious to me too, but 15288 ns = 0.015 ms, which should not be enough to disturb the overall system latency.

> [27622.091908] hda-intel 0000:00:1b.0: Unstable LPIB (65536 >= 8192); disabling LPIB delay counting

That is okay. It indicates that "position_fix=1" won't work reliably, which we already knew.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

(sort of) Good news!

* Installed an Ubuntu Precise LTS system, from scratch, in an empty partition:

foobar@dale:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise

* Tried to break audio by any means, I couldn't.

* Installed the suggested kernel from raring, as in:

foobar@dale:~$ uname -a
Linux dale 3.8.0-27-generic #40~precise3-Ubuntu SMP Fri Jul 19 14:38:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

foobar@dale:~$ apt-cache policy linux-image-3.8.0-27-generic
linux-image-3.8.0-27-generic:
  Installed: 3.8.0-27.40~precise3
  Candidate: 3.8.0-27.40~precise3
  Version table:
 *** 3.8.0-27.40~precise3 0
        500 http://ar.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages
        100 /var/lib/dpkg/status

* Opened mumble, ran the audio wizard a couple of times, and also played the sample ogg from the default "Examples" folder, and audio playback died.

Attaching pulseaudioverbose.log, obtained by following the ubuntu wiki instructions.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Changed in alsa-driver (Ubuntu):
importance: Undecided → Medium
affects: alsa-driver (Ubuntu) → linux (Ubuntu)
tags: added: performing-bisect
Changed in linux (Ubuntu Raring):
importance: Undecided → Medium
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Raring):
status: New → Incomplete
summary: - [Realtek ALC889] - Audio Playback Unavailable
+ [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable
Changed in linux (Ubuntu Raring):
status: Incomplete → Invalid
Changed in alsa-driver (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Saucy):
status: Incomplete → Won't Fix
Rolf Leggewie (r0lf)
Changed in alsa-driver (Ubuntu Raring):
status: New → Won't Fix
Rolf Leggewie (r0lf)
Changed in alsa-driver (Ubuntu Saucy):
status: New → Won't Fix
Changed in linux (Ubuntu):
status: Incomplete → Expired
Changed in alsa-driver (Ubuntu):
status: Incomplete → Expired
Changed in linux (Ubuntu):
status: Expired → New
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Incomplete
Changed in alsa-driver (Ubuntu Vivid):
importance: Undecided → Medium
Changed in linux (Ubuntu Vivid):
importance: Undecided → Medium
77 comments hidden view all 157 comments
Revision history for this message
Natalia Bidart (nataliabidart) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected vivid
description: updated
Revision history for this message
Natalia Bidart (nataliabidart) wrote : IwConfig.txt

apport information

Revision history for this message
Natalia Bidart (nataliabidart) wrote : JournalErrors.txt

apport information

Revision history for this message
Natalia Bidart (nataliabidart) wrote : Lspci.txt

apport information

Revision history for this message
Natalia Bidart (nataliabidart) wrote : Lsusb.txt

apport information

Revision history for this message
Natalia Bidart (nataliabidart) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Natalia Bidart (nataliabidart) wrote : ProcEnviron.txt

apport information

Revision history for this message
Natalia Bidart (nataliabidart) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Natalia Bidart (nataliabidart) wrote : ProcModules.txt

apport information

Revision history for this message
Natalia Bidart (nataliabidart) wrote : PulseList.txt

apport information

Revision history for this message
Natalia Bidart (nataliabidart) wrote : UdevDb.txt

apport information

Revision history for this message
Natalia Bidart (nataliabidart) wrote : UdevLog.txt

apport information

Revision history for this message
Natalia Bidart (nataliabidart) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu Vivid):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.1 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc3-vivid/

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

As requested, tested kernel 4.1.0-040100rc3-generic. Audio playback is still lost.

See attached verbose output from pulseaudio, including the line that makes all sound go away:

(2356.093| 0.000) D: [alsa-sink-ALC889 Analog] protocol-native.c: max_request changed, trying to update from 70272 to 71292.
(2356.093| 0.000) D: [alsa-sink-ALC889 Analog] protocol-native.c: Notifying client about increased tlength
(2356.093| 0.000) D: [alsa-sink-ALC889 Analog] alsa-sink.c: Latency set to 341.33ms
(2356.093| 0.000) D: [alsa-sink-ALC889 Analog] alsa-sink.c: hwbuf_unused=4
(2356.093| 0.000) D: [alsa-sink-ALC889 Analog] alsa-sink.c: setting avail_min=737
(2356.268| 0.175) I: [alsa-sink-ALC889 Analog] alsa-sink.c: Underrun!
(2356.268| 0.000) I: [alsa-sink-ALC889 Analog] alsa-sink.c: Increasing wakeup watermark to 331.31 ms
(2356.447| 0.178) I: [alsa-sink-ALC889 Analog] alsa-sink.c: Underrun!

tags: added: kernel-bug-exists-upstream
Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Changed in alsa-driver (Ubuntu):
status: Expired → Confirmed
Changed in alsa-driver (Ubuntu Vivid):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

It looks like we were bisecting between 3.8.13.1 and 3.8.13.2 a while back. It might be best to pick that up again. I'll set up a bisect and post a test kernel shortly.

Changed in alsa-driver (Ubuntu Saucy):
importance: Undecided → Medium
Changed in alsa-driver (Ubuntu Raring):
importance: Undecided → Medium
Changed in alsa-driver (Ubuntu):
importance: Undecided → Medium
no longer affects: alsa-driver (Ubuntu Raring)
no longer affects: alsa-driver (Ubuntu Saucy)
no longer affects: linux (Ubuntu Raring)
no longer affects: linux (Ubuntu Saucy)
Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Thanks Joseph. Just FYI, I will have access to this computer for 2 weeks, then I may not be able to access it anymore for a month or two. So as soon as you have the kernels for bisect, I'll be happy to try those.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I restarted the bisect between v3.8.13.1 and 3.8.13.2.

I built a test kernel up the following commit:
37e78b62f9895480779ad92dd110a60f6ce51847

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1201528/

Can you test this kernel and see if it exhibits the bug?

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Tested kernel 3.8.13-03081301-generic

It was not easy, but audio did break. I have to use hangouts for a while. Attaching pulseaudio verbose log.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

I see from comment #93 that back then I couldn't break audio, I guess because I did not try hangout at the time.

From now on I will use hangout for every test, since it seems to be the most effective way of breaking audio. The main issue is that if audio does not break, it may be because I did not stress audio enough, not because is actually working :-/

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you confirm the 3.8.13.1 kernel does not have this bug. That way we know we are bisecting between the correct versions.

3.8.13.1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.13.1-raring/

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

From IRC:

16:20 < nessita> jsalisbury, just wanted to sync about the bisect we're doing for LP: #1201528, since I'm now in 3.8.13.1 and audio died with the underrun error. So I re-read all the comments and noticed that in commnet #39 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201528/comments/39) I reproduced the issue with kernel 3.8.0-27-generic

16:21 < nessita> I'm now installing latest 3.7 from http://kernel.ubuntu.com/~kernel-ppa/mainline/ which is 3.7.10 and see if audio breaks, will report in the bug

So, in summary:

Kernel 3.8.13.1 -> AUDIO BREAKS

Kernel 3.7.10 -> audio does not break

Will try other versions of 3.8.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

As per anoter IRC conversation,

* tested kernel 3.8.0 final (3.8.0-030800) and AUDIO BREAKS (it was hard to reproduced, seems like the underruns are less "extreme"). See verbose pulseaudio log please.

* tested kernel 3.7.0 final (3.7.0-030700) and audio does not break (attached log the same).

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

We should also test some of the 3.8 release candidates to know which exact one introduced the regression. Once we know that, we can start the bisect.

Can you test the following kernels and post back? We are looking for the first kernel version that exhibits this bug:

v3.8-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc4-raring/

If v3.8-rc4 does not exhibit the bug then test v3.8-rc6:
v3.8-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc6-raring/

If v3.8-rc4 does exhibit the bug then test v3.8-rc2:
v3.8-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc2-raring/

Thanks in advance!

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Hello! Reporting back:

Tested kernel 3.8.0-030800rc4 and audio BREAKS

Then, as requested, tested kernel 3.8.0-030800rc4 and audio BREAKS

Attaching pulseaudio verbose logs. In both cases audio breaks when pulseaudio reports:

[alsa-sink-ALC889 Analog] alsa-sink.c: Underrun!

Side note: Just to be super sure, what's the kernel I should have installed to cross check it keeps working? should that be 3.7.0 or 3.7.10?

Thanks

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Sorry, the second rc4 is obviously rc2, see attached log for confirmation, I always run the pulseaudio daemon with:

LANG=C pulseaudio -vvvv --log-time=1 > ~/pulseverbose-`uname -r`.log 2>&1

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you now test v3.8-rc1? If it exhibits the bug we can bisect between 3.7 final and 3.8-rc1. The v3.8-rc1 kernel can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc1-raring/

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

[alsa-sink-ALC889 Analog] alsa-sink.c: Underrun!

this seem not alsa driver, it occur whe client did not supply audio and server has nothing to write

in theory, the server have to call snd_pcm_foreward to recover

http://cgit.freedesktop.org/pulseaudio/pulseaudio/log/src/modules/alsa/alsa-sink.c?qt=grep&q=underrun

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

you can add pa_alsa_dump() immediately after pa_log_info("Underrun!") to verify appl_ptr is behind hwptr since those pulseaudio clients did not supply sufficient audio to the server

the server seem have no ways to recover since it can not write any data which affect the timing
it just hope the client can supply the missing data at later time

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Audio BREAKS with 3.8.0-030800rc1-generic, attaching verbose log for pulseaudio

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I started a kernel bisect between v3.7 final and v3.8-rc1. The kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
6be35c700f742e911ecedd07fcc43d4439922334

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1201528

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Hello Joseph!

Thanks a lot for the bisect work. As I mentioned earlier in the backlog, I'm not at home with the troubling computer for 2 months, but I commit to test this kernel as soon as I get back. I'm very interested to have this issue sorted out (or at least debugged) so I will test the new kernel ASAP, but that will be in early August.

Thanks!

Revision history for this message
Andy Whitcroft (apw) wrote : Closing unsupported series nomination.

This bug was nominated against a series that is no longer supported, ie vivid. The bug task representing the vivid nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Vivid):
status: Confirmed → Won't Fix
Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Hello all,

First of all, sorry I did not try the kernel that Joseph provided over a year ago, I've been traveling and not having my desktop computer close.

I'm now settled in a location with my desktop computer as my daily and main computer, and I'm still seeing this bug occur.

I'm running ubuntu xenial 16.04 with the stock kernel:

nessita@dali:~$ uname -a
Linux dali 4.4.0-109-generic #132-Ubuntu SMP Tue Jan 9 19:52:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

And audio breaks just like I've posted earlier:

( 71.143| 0.000) I: [alsa-sink-ALC889 Analog] alsa-sink.c: Underrun!

I've recorded a new log file from running pulseaudio with verbose output and I've attached it to this bug.

tags: added: xenial
removed: raring vivid
Displaying first 40 and last 40 comments. View all 157 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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