From owner-freebsd-current@freebsd.org  Fri Sep 30 05:33:32 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB39CC0332A
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 30 Sep 2016 05:33:32 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 74539199
 for <freebsd-current@freebsd.org>; Fri, 30 Sep 2016 05:33:32 +0000 (UTC)
 (envelope-from hps@selasky.org)
Received: from laptop015.home.selasky.org (unknown [62.141.129.119])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 7D1281FE022;
 Fri, 30 Sep 2016 07:33:29 +0200 (CEST)
Subject: Re: /dev/dsp got more sensitive about writes?
To: Benjamin Kaduk <kaduk@MIT.EDU>, freebsd-current@freebsd.org
References: <alpine.GSO.1.10.1609291901130.5272@multics.mit.edu>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <5f384b41-23a1-1e27-1384-e30976e20a12@selasky.org>
Date: Fri, 30 Sep 2016 07:38:22 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <alpine.GSO.1.10.1609291901130.5272@multics.mit.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2016 05:33:32 -0000

On 09/30/16 01:01, Benjamin Kaduk wrote:
> Hi all,
>
> I've updated from r302211 (June 26) to r306427 (yesterday), and the
> behavior of audio/sox (in its play(1) alias) seems to have changed.  I
> used to be able to suspend play(1) for an arbitrary period of time and
> have the output continue when it was foregrounded again.
>
> Now, it seems that I can only suspend it for 4-5 seconds and retain
> playback; for longer sleeps, I get
>
> [1]+  Stopped                 play 01\ Mary\ Hynes.wav
> [root@glossolalia ...]# sleep 5; fg
> play 01\ Mary\ Hynes.wav
> play FAIL sox: `/dev/dsp' error writing output file: Invalid argument
> Done.
>
>
> Wrapping play(1) in truss seems to change things, though; in that case, I
> can sleep for at least two minutes and still recover playback.  So that
> makes it a bit hard to see what's going on.
>
> I will note that I did not upgrade ports/packages after the base upgrade,
> so the sox binary in use is potentially somewhat stale.
>
> Does that ring any bells for anyone?

Hi,

Maybe you could ktrace the program. SOX has a bad behaviour that it 
writes one and one sample through GIO when using /dev/dsp. I once made a 
patch for it, but it was never upstreamed.

--HPS