From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 18 03:29:55 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E02F106564A for ; Sat, 18 Feb 2012 03:29:55 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 336078FC0A for ; Sat, 18 Feb 2012 03:29:55 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q1I3TskU039948 for ; Fri, 17 Feb 2012 19:29:54 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <4F3F1B31.7070109@rawbw.com> Date: Fri, 17 Feb 2012 19:29:53 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0) Gecko/20120202 Thunderbird/10.0 MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Why /dev/dsp can get into "Device busy" state? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Feb 2012 03:29:55 -0000 At some point, after killing audio playing app with Ctrl-C, I am unable to play sound again with the same app: Can't open audio device /dev/dsp: Device busy But after closing virtual box windows guest, sound is working again. What bothers me, why audio device can even become busy? Isn't it supposed to mix all inputs no matter how many? It usually works fine with many apps playing sound at the same time. What exactly is the condition that causes sound device to become busy? Driver in use is snd_es137x. fstat /dev/dsp doesn't show who opened sound device for some reason. Yuri