Folks.  I heard on IRC others are seeing this as well:

I'm using FreeBSD 5.0-CURRENT #2: Thu Jan  9 22:49:45 CET 2003 on i386,
but it used to happen since at least December, maybe even November (I'm
always using more or less recent -CURRENT's).
I didn't happen before, so I can be rather sure it's not the xmms binary
which causes the error, since I haven't changed anything in regard to
XMMS since August:
-r-xr-xr-x  1 root  wheel  974196 Aug 23 12:24 xmms
and this error definitely didn't occur before November.

This is my sndstat, if of interest:
FreeBSD Audio Driver (newpcm)
Installed devices:
pcm0: <CMedia CMI8738> at io 0xd800 irq 10 (1p/1r/2v channels duplex default)

hw.snd.targetirqrate: 32
hw.snd.report_soft_formats: 1
hw.snd.verbose: 1
hw.snd.unit: 0
hw.snd.maxautovchans: 5
hw.snd.pcm0.buffersize: 16384
hw.snd.pcm0.vchans: 2
hw.snd.pcm0.spdif_enabled: 0

Anyways, here's the problem description:

After several hours/days of uptime (2 days now)  and approx.
12 hours/day sound usage with XMMS and like hundrets of MP3 songs played,
/dev/dsp just disappears.

It always happens after XMMS finnished an MP3 song and wants to play the
next one (also on songs it successfully played before).  This fails,
because of these error messages:

** WARNING **: oss_open(): Failed to open audio device (/dev/dsp):
Operation not supported by device
** WARNING **: oss_open(): Failed to open audio device (/dev/dsp): No
such file or directory

I then mknod a dsp device with the major/minor of dsp in / and s-linked
/dev/dsp to /dsp.  xmms then reports "Device busy".

When I then symbolically link /dev/dsp to one of the dspX.X devices,
XMMS can play sound for some more time, but then these are disappearing
as well.

Is this a devfs bug?  I almost think so, but I'm not sure.

Alex

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to