-----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-----
On Fri, 2005-04-15 at 01:22 +0200, Christian Kujau wrote:
> maybe some guru can shed some light on what's going on in xmms-oops.txt
> and tell me who's to bug here :->
Fixed in 2.6.11.7.
Lee
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Lee Revell wrote:
>
> Fixed in 2.6.11.7.
>
thank you & sorry for the noise.
Christian.
- --
BOFH excuse #20:
divide-by-zero error
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCXwfv+A7rjkF8z0wRAnnKAJ0T93Q/IHCKmyFiLkhnvBU2a06cPgCdHRRo
7rBaIbXcYc7L5CBEvoAr93E=
=xyAE
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jesper Juhl wrote:
>
> ^^^^^ you should send such info inline in the email - having to go check
> external links makes a lot of people ignore the stuff right then and
yeah, but the oops doesn't wrap at 80 chars itsself and often oopses are
hardly readable inline.
> Btw: I believe this is fixed in 2.6.11.7 - from the Changelog :
>
> <[email protected]>
> [PATCH] Fix Oops with ALSA timer event notification
oh, this sounds good. strange though, that my 2.6.11-gentoo-r5 (whatever
they've patched in there) *never* oopsed the days ago but all of a sudden
started to oops yesterday....
thank you,
Christian.
- --
BOFH excuse #131:
telnet: Unable to connect to remote host: Connection refused
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCXwem+A7rjkF8z0wRAuXSAJ4tZujWF0H5Da5o2J6yfzZQJolhPACgiKUR
YknU154MUkPEB52FuYTTF50=
=5yoy
-----END PGP SIGNATURE-----
On Fri, 2005-04-15 at 02:16 +0200, Christian Kujau wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Lee Revell wrote:
> >
> > Fixed in 2.6.11.7.
> >
>
> thank you & sorry for the noise.
No need to apologize, this is not noise. Always err on the side of
reporting the bug. It's much better to deal with duplicate bug reports
than have bugs go unreported.
Lee
On Fri, 15 Apr 2005, Christian Kujau wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jesper Juhl wrote:
> >
> > ^^^^^ you should send such info inline in the email - having to go check
> > external links makes a lot of people ignore the stuff right then and
>
> yeah, but the oops doesn't wrap at 80 chars itsself and often oopses are
> hardly readable inline.
>
I would still suggest including the info inline and then if you think it's
needed /also/ provide the link you did - then you've covered all bases :)
> > Btw: I believe this is fixed in 2.6.11.7 - from the Changelog :
> >
> > <[email protected]>
> > [PATCH] Fix Oops with ALSA timer event notification
>
> oh, this sounds good. strange though, that my 2.6.11-gentoo-r5 (whatever
> they've patched in there) *never* oopsed the days ago but all of a sudden
> started to oops yesterday....
>
Some bugs are like that, especially when they involve race conditions or
timers.. Anyway, if you could test 2.6.11.7 (and perhaps also 2.6.12-rc*)
to verify that the issue is indeed fixed, then I believe that would be
appreciated :)
--
Jesper
Christian Kujau wrote:
> oh, this sounds good. strange though, that my 2.6.11-gentoo-r5 (whatever
> they've patched in there) *never* oopsed the days ago but all of a sudden
> started to oops yesterday....
Probably because you changed alsa-lib versions. By the way, it is fixed in
gentoo-sources-2.6.11-r6.
Daniel
At Thu, 14 Apr 2005 19:35:19 -0400,
Lee Revell wrote:
>
> On Fri, 2005-04-15 at 01:22 +0200, Christian Kujau wrote:
> > maybe some guru can shed some light on what's going on in xmms-oops.txt
> > and tell me who's to bug here :->
>
> Fixed in 2.6.11.7.
Also, the latest CVS alsa-lib checks the timer protocol version to
avoid this Oops with the older kenel. 1.0.9-rc3 is planned to be
released soon, so wait for a moment...
Takashi
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Takashi Iwai wrote:
>
> Also, the latest CVS alsa-lib checks the timer protocol version to
> avoid this Oops with the older kenel. 1.0.9-rc3 is planned to be
> released soon, so wait for a moment...
um, i'll wait for the next release as i don't track alsa-cvs. but i do
track 2.6-BK (again) and the oops is gone ;-)
Jesper Juhl wrote:
>> yeah, but the oops doesn't wrap at 80 chars itsself and often oopses
>> are hardly readable inline.
>
> I would still suggest including the info inline and then if you think
> it's needed /also/ provide the link you did - then you've covered all
> bases :)
will do, next time 8-)
thanks to all involved for all your replies,
Christian.
- --
BOFH excuse #388:
Bad user karma.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCX9WT+A7rjkF8z0wRAlp2AJ0doKLm4OsK2i8nNx6uezrcfPF15QCeNkuO
eVCEuP0U5LrUOToHXEb6cBs=
=Feow
-----END PGP SIGNATURE-----