I am running FreeBSD 6.2 (i386) with an Intel ICH5. The latest versions of OSS (including 4.0 build 1002) cause my computer to crash when playing audio through the vmix system. I have tried xmms, mplayer and amarok. Sound will play for a few seconds and then the crash will occur. This does not seem to happen when using the real channel only.

The last version of OSS I have found not to make my computer crash is 4.0rc8 build 190. I tried several releases after this one and they produced the same results, but I figured it was just a bug that would get ironed out during the release process.

P.S. are the virtual channels able to be dynamically allocated yet in FreeBSD? (i.e. set everything to /dev/dsp and a virtual channel will be assigned)

I'm surprised that you're getting panics via VMIX. You can resort to softoss by editing /usr/lib/oss/etc/installed_drivers

As for dynamic audio channel allocation - the code won't work unless there is work done at the kernel level. The current EVENT_HANDLER() concept will not work for OSS because event handling doesn't care about whether the device is a input or output device. In OSS, we need to be sure that when a device is opened for Output, the new device allocated by event_handling is an output device.

veneficus wrote:I have the exact same problem with Nvidia CK8S using vmix.FreeBSD 6.2-release and oss v4.0 build 1002

You need to be more specific - how did the machine crash - what app were you playing - where's the ossinfo output? We cannot reproduce any crashes on our FreeBSD 6.2-RELEASE machines with the ICH/Nvidia CK8S driver.

However you should be able to look at the crash, then look at /usr/lib/oss/build and fix up any problems related to FreeBSD kernel interface by changing osscore.c and running the install.sh script.

Sorry for the lack of info. I just saw a problem that I have too and thought to let you know.
This isn't a big problem for me because I use esound for mixing and keep vmix disabled.
When I output to vmix-channel it seems to work but after a while my system freezes and reboots.
It seems to happen with all programs that play sound continuously (players like xmms,audacious, mplayer, ..)

I still get the same type of crash with build 1003 on FreeBSD 6.2. Same ICH5 with an AD1888 AC97 codec.

I built this version from the FreeBSD ports tree, but it shouldn't matter. I tried playing a song in xmms through vmix. It played a few seconds then everything froze - the sound stopped and the desktop was still visible but it did not react to the mouse or keyboard. Then a few seconds later the computer rebooted itself.

I just tried the official package for 4.0 build 1004, same problem. The computer rebooted almost immediately after I hit play on xmms trying to play a small mp3 file with only an xterm running inside of twm. I haven't been able to obtain any memory dumps...the computer just reboots immediately.

I was getting some errors with softoss too in build 1003...haven't tried softoss in 1004. I actually went back to using 4.0rc8 build 190 for the time being. The errors were:

These messages repeated several times. Sometimes amarok, xmms or mplayer would not start playing saying that the audio device was busy. Then if I hit the play button a second time it would start playing. I never got any crashes because of this, the audio device would just seemingly be busy.

BSDKaffee wrote:I just tried the official package for 4.0 build 1004, same problem. The computer rebooted almost immediately after I hit play on xmms trying to play a small mp3 file with only an xterm running inside of twm. I haven't been able to obtain any memory dumps...the computer just reboots immediately.

I was getting some errors with softoss too in build 1003...haven't tried softoss in 1004. I actually went back to using 4.0rc8 build 190 for the time being. The errors were:

These messages repeated several times. Sometimes amarok, xmms or mplayer would not start playing saying that the audio device was busy. Then if I hit the play button a second time it would start playing. I never got any crashes because of this, the audio device would just seemingly be busy.

Hi,

The code for memory allocation is straightforward and I really don't know why the drivers fail to allocate memory. We need some help on FreeBSD...that's for sure.