From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: ALSA Oops (triggered by xmms)
Date: Fri, 15 Apr 2005 01:22:26 +0200 [thread overview]
Message-ID: <425EFB32.2010000@g-house.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
howdy,
yesterday i hit an Oops when i tried to play an mp3 with xmms. nothing
unusual. the thing is - i've not changed the kernel (2.6.11-gentoo-r5) for
a while, but changed some (multimedia related) libs on my system. xmms
just segfaults and it all seems to be a proper userspace bug (even xmms
told me so). i really suspect xmms or the changed libs.
but i still believe in the old proverb my grandma used to say: "no
userspace app should make the kernel oops." but yesterday it did:
http://nerdbynature.de/bits/prinz/2.6.11-gentoo-r5/
this is 100% reproducable whenever i use the ALSA sounddriver in xmms.
when i use "mpg321 -o alsa ..." everything is ok.
maybe some guru can shed some light on what's going on in xmms-oops.txt
and tell me who's to bug here :->
thank you,
Christian.
- --
BOFH excuse #289:
Interference between the keyboard and the chair.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCXvsy+A7rjkF8z0wRAi5qAKCHXt/BSXHJdiMvYbf6SWnEIuFwkwCgmpmA
jRpOB7REfh99kMVaMdyIniw=
=rSNT
-----END PGP SIGNATURE-----
next reply other threads:[~2005-04-14 23:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 23:22 Christian Kujau [this message]
2005-04-14 23:35 ` ALSA Oops (triggered by xmms) Lee Revell
2005-04-14 23:35 ` Lee Revell
2005-04-15 0:16 ` Christian Kujau
2005-04-15 0:21 ` Lee Revell
2005-04-15 8:54 ` [Alsa-devel] " Takashi Iwai
2005-04-15 14:54 ` Christian Kujau
[not found] ` <Pine.LNX.4.62.0504150150240.3466@dragon.hyggekrogen.localhost>
2005-04-15 0:15 ` Christian Kujau
2005-04-15 0:29 ` Jesper Juhl
2005-04-15 8:19 ` Daniel Drake
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=425EFB32.2010000@g-house.de \
--to=evil@g-house.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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.