4.10-RELEASE-p3 i386 problem with /dev/dsp

Roman Neuhauser neuhauser at sigpipe.cz
Wed May 25 00:59:42 PDT 2005

# spoerlein at informatik.uni-wuerzburg.de / 2005-05-24 21:27:19 +0200:
> On Mon, 23.05.2005 at 16:10:03 +0200, Roman Neuhauser wrote:
> > I have a machine with FreeBSD 4.10-RELEASE-p3 i386 (450MHz P3/Celeron)
> > that has been running just fine, but after ~ 120 days something
> > happened to /dev/dsp, and I can no longer play mp3s. A restart would
> > most probably fix it, but I'd like to know if it's possible to determine
> > (and fix) the issue on a running system. Yes, I'm fond of my uptime
> > ("up 133 days, 20:04", including an X session), but I'd also like to know if
> > this is recoverable or requires the windows-style bandaid.
> Back in the days, this used to happen from time to time. Somehow
> processes no longer could open /dev/dsp, but no other process had it
> open (verified with lsof and fstat).

    But ktrace / kdump say the device has been open successfully, and
    it's not before many writes (128 bytes each) return success that it
    starts returning -1 with EINVAL.
> Looks like you need to reboot ...

    Maybe this is a different problem, correctable without rebooting.
    Of course, there isn't really any reason not to reboot it, but
    I'd like to understand the problem first.

    I understand that such a problem with 4.x won't draw much attention
    these days. I just happen to enjoy 4.x so much I have it on all but
    two boxes (a colleague of mine who runs 5.x had several panics
    during the four months this 4.10 needed to build enough entropy to
    give up sound).

How many Vietnam vets does it take to screw in a light bulb?
You don't know, man.  You don't KNOW.
Cause you weren't THERE.             http://bash.org/?255991

More information about the freebsd-stable mailing list