Audio has occasional skips/dropouts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I haven't been able to determine a pattern to this yet, but ever since loading two of my machines with Karmic, I've been having audio drop-outs.
I am *not* using Pulseaudio.
It affects all music players - Audacious, Exaile, even the command-line 'play' utility that comes with SoX - and probably other audio sources as well. The symptoms are simple: I get little "hiccups" in the sound now and again, either the audio is skipping forward by some small, random amount, like listening to a cassette player with someone tapping the "fast forward" button now and again, or by dropping out entirely, as in silence for a brief period.
In its worst case, audio dropped out for several *seconds*, during which time one of the two CPU cores was pegged at 100%.
I have examined my system logs, dmesg, and watched for errors on the command line. I have found nothing at all except for a single clue: On a *completely idle* machine, SoX kept warning me of buffer underruns while experiencing these audio hiccups:
abe@cardinal:~$ play [filename hidden]
File Size: 1.56M Bit Rate: 102k
Encoding: MPEG audio Info: 1962
Channels: 2 @ 16-bit Track: 6
Samplerate: 44100Hz Album: [hidden]
Replaygain: off Artist: [hidden]
Duration: 00:02:01.70 Title: [hidden]
In:0.15% 00:00:00.19 [00:02:01.52] Out:4.10k [ | ] Clip:0 play WARN alsa: under-run
In:0.15% 00:00:00.19 [00:02:01.52] Out:4.44k [ | ] Clip:0 play WARN alsa: under-run
In:3.82% 00:00:04.64 [00:01:57.06] Out:218k [ ==|== ] Clip:0 play WARN alsa: under-run
In:21.7% 00:00:26.38 [00:01:35.33] Out:1.26M [ -=|=- ] Clip:0 play WARN alsa: under-run
In:42.1% 00:00:51.27 [00:01:10.43] Out:2.45M [ | ] Clip:0 play WARN alsa: under-run
The machines in question both carry a Gigabyte K8U-939 mainboard with an Athlon 64x2 3800+ processor and 1GB RAM. One machine has a Creative SB Live! sound card, the other is using on-board audio. Both have reasonably fast SATA hard disks and onboard RTL-8139-based ethernet devices. Clearly, they have more than sufficient computing power for the tack at hand.
Both machines were running Jaunty before, without any problems. Both received a fresh install of the final/official release of Karmic - that is, I did not "upgrade" them directly from Jaunty.
ProblemType: Bug
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Live [Dell Sound Blaster Live!], device 0: emu10k1x [EMU10K1X Front]
Subdevices: 1/1
Subdevice #0: subdevice #0
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Live'/'Dell Sound Blaster Live! at 0xc000 irq 21'
Mixer name : 'SigmaTel STAC9708,11'
Components : 'AC97a:83847608'
Controls : 44
Simple ctrls : 26
Date: Fri Nov 6 10:45:19 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
vboxnet0 no wireless extensions.
NonfreeKernelMo
Package: linux-image (not installed)
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux-meta
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
(polkit-
(xfce4-
(xfce4-
dmi.bios.date: 12/01/2005
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: M1689D
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSof
tags: | added: kj-triage |
tags: | added: acpi-method-return |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
tags: | added: b73a1py79 |
[This is an automated message. Apologies if it has reached you inappropriately.]
This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.
If this bug really is a bug in the linux-meta package you can move it back to linux-meta and set the Status to Confirmed, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.