It looks like my initial conclusion was wrong. The oopses only come when using savemixer, loading and unloading modules has nothing to do with it. Running ossmix without any parameters will cause a segfault. I downgraded to the 2008-07-01 version, disabled vmix0-enable, ran savemixer, and then installed 2008-09-08. The ossmix and savemixer utilities work perfectly when the old modules are loaded, but even with vmix0-enable disabled before loading the new modules, it had no effect to the problem. osstest also works, so it just seems that things go bad only when something tries to change or access the mixing.
Here is the rather strange segfault that ossmix produces: ossmix[3100]: segfault at 10 ip a7ea2063 sp afd96c38 error 4 in libc-2.8.90.so[a7e30000+13b000] Thanks, Teran (sega01) On Tue, Sep 9, 2008 at 07:06, Hannu Savolainen <[EMAIL PROTECTED]> wrote: > Hi, > > Can you turn off the vmixN-enable (say vmix0-enable) setting using > ossmix/ossxmix. Does it still crash after that? > > Best regards, > > Hannu > --------- > Teran McKinney write: >> Hi, >> >> I have been using OSS lately and have been very pleased with it. Its >> driver support is phenomenal, and Freenode's #oss is very helpful. >> >> After updating from a snapshot from 2008-07-01 to 2008-09-06, I began >> seeing strange kernel oopses on one of my boxes. I use Wine to play >> Team Fortess 2, and even running Wine at all (it is configured to use >> OSS) caused the whole system to crash. I traced the problem back to >> OSS, but was confused because ossrecord and ossplay worked perfectly. >> Even starting syslog-ng would give a (nonfatal) kernel oops, so it >> seems to be quite a low level bug at first glance. Reverting to the >> freshly built 2008-07-01 snapshot works fine, even with the new >> changes in my build script. Unloading the OSS modules was the easiest >> way to get a (nonfatal) oops, as it would do so constently. After >> spending a few hours reverting back to older builds and trying to find >> which change broke it, I decided that I should just post a bug report >> for it (I would love to help diagnose what broke this exactly, but I >> am quite busy). Bugzilla gave a Perl error when I tried to register, >> so I was refered to this list by cesium (who was also very helpful >> giving suggestions and assistance with Mercurial usage). >> >> Here is the oops: >> ftp://icadyptes.go-beyond.org/other/oss-opps.txt >> >> My build script: >> ftp://icadyptes.go-beyond.org/icadyptes/abs/extra/multimedia/oss/PKGBUILD >> >> I did enough testing to say that the problem was inserted between >> 2008-07-01 and 2008-08-13 (for some reason, many dates did not work to >> revert back to in Mercurial). >> >> Let me know if you need any more information or someone to test patches. >> >> Thanks, >> Teran (sega01) >> _______________________________________________ >> oss-devel mailing list >> oss-devel@mailman.opensound.com >> http://mailman.opensound.com/mailman/listinfo/oss-devel >> > > _______________________________________________ > oss-devel mailing list > oss-devel@mailman.opensound.com > http://mailman.opensound.com/mailman/listinfo/oss-devel > _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
