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

Reply via email to