From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0001179]: alsa-lib 1.0.9 breaks snd_hda_intel
Date: Mon, 20 Jun 2005 10:45:14 +0200 [thread overview]
Message-ID: <bf12594a8ea514cb78d4a7e2d80fbcc9@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1179>
======================================================================
Reported By: theoneandonlysm
Assigned To:
======================================================================
Project: ALSA - lib
Issue ID: 1179
Category: 0_general
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 06-10-2005 19:08 CEST
Last Modified: 06-20-2005 10:45 CEST
======================================================================
Summary: alsa-lib 1.0.9 breaks snd_hda_intel
Description:
I upgraded alsa (lib, tools, oss) 1.0.8 to 1.0.9 through Slackware's
package update and noticed that aRts in kde did not produce any sound even
though no errors in arts was reported.
I uninstalled the alsa-lib package and compiled the 1.0.8 sources and
sound worked again (with self-compiled 1.0.9 drivers on kernel 2.6.11.11).
Compiling and installing alsa-lib 1.0.9 once again caused sound to stop
functioning.
dmesg gives me no errors, and I am not certain where else to look. The
only clue I get is from mplayer while playing an audio file, where I get
continual output of:
alsa-space: xrun of at least 0.002 msecs. resetting stream
alsa-space: xrun of at least 0.002 msecs. resetting stream
alsa-space: xrun of at least 0.002 msecs. resetting stream
alsa-space: xrun of at least 0.004 msecs. resetting stream
alsa-space: xrun of at least 0.004 msecs. resetting stream
alsa-space: xrun of at least 0.002 msecs. resetting stream
alsa-space: xrun of at least 0.002 msecs. resetting stream
my lsmod:
vmnet 27812 2
parport_pc 22980 1
vmmon 105260 0
snd_pcm_oss 49312 0
snd_mixer_oss 18304 1 snd_pcm_oss
snd_hda_intel 14336 1
snd_hda_codec 69248 1 snd_hda_intel
snd_pcm 83716 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer 22276 1 snd_pcm
snd 50532 8
snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
snd_page_alloc 8068 2 snd_hda_intel,snd_pcm
lp 8836 0
parport 21440 2 parport_pc,lp
nfsd 91464 8
exportfs 5120 1 nfsd
nfs 96044 1
lockd 61992 3 nfsd,nfs
sunrpc 130500 5 nfsd,nfs,lockd
vfat 11648 1
fat 36252 1 vfat
i915 18176 1
drm 61204 2 i915
intel_agp 20380 1
agpgart 29488 3 drm,intel_agp
hw_random 4884 0
rtc 10828 0
ehci_hcd 29576 0
usblp 11648 0
uhci_hcd 30480 0
usbcore 107384 4 ehci_hcd,usblp,uhci_hcd
======================================================================
----------------------------------------------------------------------
theoneandonlysm - 06-20-05 03:46
----------------------------------------------------------------------
aRts does not seem to be causing the problem - it seems that when aRts or
any other program uses alsa to access the sound device, the problem
persists; however, explicitly setting programs to use OSS (through the OSS
compatibility modules) resolves the problem.
----------------------------------------------------------------------
sally - 06-20-05 10:45
----------------------------------------------------------------------
explicitly setting programs to use OSS resolves the problem.
Do you mean "gets around the problem" or that this trick enables alsa to
work correctly?
I am starting to suspect this is a dmix problem. I will post more once I
have nailed it down.
Issue History
Date Modified Username Field Change
======================================================================
06-10-05 19:08 theoneandonlysmNew Issue
06-13-05 13:09 tiwai Note Added: 0005008
06-19-05 12:30 sally Note Added: 0005088
06-20-05 03:46 theoneandonlysmNote Added: 0005092
06-20-05 10:45 sally Note Added: 0005094
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-06-20 8:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 8:45 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-01 0:05 [ALSA - lib 0001179]: alsa-lib 1.0.9 breaks snd_hda_intel bugtrack
2005-12-30 3:25 bugtrack
2005-07-01 19:53 bugtrack
2005-06-25 3:11 bugtrack
2005-06-21 9:13 bugtrack
2005-06-20 23:37 bugtrack
2005-06-20 9:23 bugtrack
2005-06-20 1:46 bugtrack
2005-06-19 10:30 bugtrack
2005-06-13 11:09 bugtrack
2005-06-10 17:08 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bf12594a8ea514cb78d4a7e2d80fbcc9@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.