After upgrading my gentoo-dev-sources kernel from 2.6.3-gentoo-r2 to 2.6.4-gentoo I discovered that both xmame and xmess would crash out with the error: xmess: pcm.c:5899: snd_pcm_mmap_commit: Assertion `frames <= snd_pcm_mmap_avail(pcm)' failed. After several recompiles I discovered that emerging xmess/xmame without ALSA support (USE="-alsa oss") resulted in xmame/xmess working fine. Obviously this is hardly an ideal soltuion so I was wondering if there was anything more that could be done. Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.50-r1 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040207-r0, 2. 6.4-gentoo) ================================================================= System uname: 2.6.4-gentoo i686 AMD Athlon(tm) XP 2400+ Gentoo Base System version 1.4.3.13p1 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -mcpu=athlon-xp -mfpmath=sse,387 -ffast-math -O3 -fstack-protector -frename-registers -fomit-frame-pointer -falign-functions=64 -funroll-loops -falign-loops=5 -falign-jumps=5 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -mcpu=athlon-xp -mfpmath=sse,387 -ffast-math -O3 -fstack-protector -frename-registers -fomit-frame-pointer -falign-functions=64 -funroll-loops -falign-loops=5 -falign-jumps=5 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://ftp.megamirror.com/pub/gentoo http://public.ftp. planetmirror.com/pub/gentoo ftp://mirror.pacific.net.au/linux/Gentoo/ http: //mirror.aarnet.edu.au/pub/gentoo/ http://gentoo.oregonstate.edu" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/overlays/portage /usr/local/overlays/bmg-gnome-current.alternative" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib alsa avi berkdb cdr crypt dvd encode foomaticdb gdbm gif gnome gtk gtk2 imlib java joystick jpeg libg++ libwww mad mikmod motif mpeg ncurses nls nptl oggvorbis opengl pam pdflib perl png python qt quicktime readline sdl slang spell ssl tcltk tcpd truetype video_cards_radeon x86 xml2 xmms xv zlib"
Created attachment 27467 [details, diff] makefile.unix / unix.mak patch to fix parallel build
Comment on attachment 27467 [details, diff] makefile.unix / unix.mak patch to fix parallel build This somehow got attached to the wrong bug. Ignore me please.
Does the problem still occur with vanilla 2.6 or even 2.4 with ALSA? I'm just trying to figure out if it is a patch we've added to the kernel or if it is ALSA itself.
I checked with vanilla development-sources 2.6.4 and found that it still wouldn't work so I then proceeded to install the new development-sources, 2.6.5-rc1, and found that ALSA seems to be working fine again. Whatever they broke in 2.6.4 looks to have been fixed in 2.6.5. I'll just have to wait until gentoo-dev-sources gets bumped to either 2.6.5-rc1 or 2.6.5 stable.
How about a RESOLVED-LATER? You can always reopen the bug at a later date.
latest versions should resolve this
just remember to update
