Bug 79858 – PCM playback on onboard ISA opl3sa2 soundcard (alsa) freezes system on 2.6.* kernels

• Product: Gentoo Linux
• Status: RESOLVED UPSTREAM

[Description Daniel Moreno 2005-01-28 08:49:34 UTC]

I've got two soundcards: a "ymfpci" one (Hoontech Soundtrack XG) and an onboard "opl3sa2" (ISA). Both work perfectly with alsa and 2.4.* kernels.

With 2.6.* kernels, ymfpci works still fine but trying to play anything thru opl3sa2 one will just freeze the system. Sometimes it'll do instantly, sometimes it allows a few seconds of (skipy) playback before freezing.

I've double-checked for resource conflicts, tried with and without ACPI and/or preemptive with no luck at all.

Reproducible: Always
Steps to Reproduce:
1. Play anything thru opl3sa2 PCM
2. Wait a few seconds at most

Actual Results:  
System freezes. Only way to get it back to work is via reset button. 

Expected Results:  
I'd be a lot happier if it just played my files or just spit some error 
instead of freezing. 

Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.3.5, 
glibc-2.3.4.20041102-r0, 2.4.28-lck1 i686) 
================================================================= 
System uname: 2.4.28-lck1 i686 Pentium II (Deschutes) 
Gentoo Base System version 1.4.16 
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Dec 10 2004, 03:29:11)] 
dev-lang/python:     2.3.4 
sys-devel/autoconf:  2.13, 2.59-r6 
sys-devel/automake:  1.5, 1.6.3, 1.8.5-r2, 1.7.9, 1.4_p6, 1.9.4 
sys-devel/binutils:  2.15.92.0.2-r1 
sys-devel/libtool:   1.5.10-r4 
virtual/os-headers:  2.4.21-r1 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-march=pentium2 -mcpu=athlon-xp -O2 -pipe -fprefetch-loop-arrays 
-fomit-frame-pointer -ffast-math" 
CHOST="i686-pc-linux-gnu" 
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" 
CXXFLAGS="-march=pentium2 -mcpu=athlon-xp -O2 -pipe -fprefetch-loop-arrays 
-fomit-frame-pointer -ffast-math" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" 
GENTOO_MIRRORS="http://distfiles.gentoo.org 
http://distro.ibiblio.org/pub/Linux/distributions/gentoo" 
LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -Wl,-z,combreloc -s" 
MAKEOPTS="" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/Video/portage_tmp" 
PORTDIR="/usr/portage" 
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" 
USE="x86 X alsa apm arts avi cdparanoia cdr cjk crypt cups dga dv dvd dvdr 
encode exif f77 fam fbcon flac font-server foomaticdb gcj gif gpm icq ieee1394 
imagemagick imap imlib insecure-drivers ipv6 jabber jack jikes jpeg kde lcms 
ldap libg++ libwww mad mbox mikmod mmx mng motif mozsvg mpeg mysql ncurses nls 
nodrm oggvorbis opengl oscar oss pam pdflib png postgres qt quicktime readline 
scanner sdl slang slp sqlite ssl svg tcpd tiff truetype truetype-fonts 
type1-fonts unicodeusb xml xml2 xprint xv zlib" 
Unset:  ASFLAGS, CBUILD, CTARGET, PORTDIR_OVERLAY

[Comment 1 Daniel Black (RETIRED) 2005-01-29 16:23:05 UTC]

have you tried the lastest version of alsa-driver?

[Comment 2 Daniel Black (RETIRED) 2005-01-29 16:23:30 UTC]

have you tried the lastest version of alsa-driver?

[Comment 3 Daniel Moreno 2005-01-30 03:56:21 UTC]

Yes. alsa-driver 1.0.8 shows exactly the same behavior on vanilla 2.6.10 kernel.

I've been testing new kernel and alsa-driver versions more or less regulary since kernel 2.6.1 and alsa 1.0.1. (or so, I'm saying by head now) And I've never seen a change.

[Comment 4 Jeremy Huddleston (RETIRED) 2005-04-21 01:44:46 UTC]

Unfortunately, I don't have that soundcard, and it doesn't look like anyone else is jumping onboard to help you, so you'll probably have better luck working out this problem upstream.  Checkout bugtrack.alsa-project.org, and let me know the bug number, so I can track it.

[Comment 5 Daniel Moreno 2005-04-21 12:45:15 UTC]

I opened a bug at "alsa-project.org" in july 2004. 9 months later they answered by asking whether the problem persists in new alsa versions or not. That's all so far. Guess I'll have to stick to 2.4.x kernels for now.

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=405