From owner-freebsd-current@FreeBSD.ORG  Tue Jul 20 08:24:02 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7304A16A4CE; Tue, 20 Jul 2004 08:24:02 +0000 (GMT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 407FE43D41; Tue, 20 Jul 2004 08:24:02 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i6K8Nrrc041129;
	Tue, 20 Jul 2004 01:23:56 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200407200823.i6K8Nrrc041129@gw.catspoiler.org>
Date: Tue, 20 Jul 2004 01:23:52 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: conrads@cox.net
In-Reply-To: <XFMail.20040719142929.conrads@cox.net>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-multimedia@FreeBSD.org
cc: freebsd-current@FreeBSD.org
Subject: Re: [amd64] Sound breakage with snd_ich driver
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2004 08:24:02 -0000

On 19 Jul, Conrad J. Sabatier wrote:
> This problem has persisted for the last several weeks now, close to a
> month or so, I would say.
> 
> Playing MP3s using madplay, everything works fine for a while, then
> suddenly I get an "output: write: Invalid argument" error each time
> madplay starts up.  Any further attempts to use sound via any method or
> app likewise fail.  Sound remains broken until a reboot.
> 
> Upgraded the system again yesterday, to the new "sound" drivers, same
> results.
> 
> I've attached truss output from one of these failed madplay runs.

I suspect that the sound driver is getting interrupt timeouts and is
marking the channel dead.  Do you see the following message in
/var/log/messages?
	 play interrupt timeout, channel dead
If so, I've seen other reports of this.

I think the chn_write() code needs some careful analysis ...