From owner-freebsd-current@FreeBSD.ORG Mon Dec 22 19:28:42 2003 Return-Path: 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 7420516A4CE; Mon, 22 Dec 2003 19:28:42 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16A9443D3F; Mon, 22 Dec 2003 19:28:41 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id hBN3Sdiw005137; Mon, 22 Dec 2003 22:28:40 -0500 (EST) Date: Mon, 22 Dec 2003 22:28:39 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Scott Long In-Reply-To: <3FE7B115.8030808@freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Robert Watson cc: current@freebsd.org Subject: Re: Looping sound output from pcm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Dec 2003 03:28:42 -0000 On Mon, 22 Dec 2003, Scott Long wrote: > Robert Watson wrote: > > I ran aim after a recent kernel update, and had a rather odd problem. I > > got an instant message from someone which resulted in a "ding" from aim. > > However, the ding never stopped dinging -- the sample repeated over and > > over again, and continues as I type. Even after the aim process exited. > > Sending additional sound output didn't make it go away either. KDE/arts, > > etc, don't seem to be involved in the problem, so it really seems like the > > kernel is looping the sample. When I try to unload pcm, I get: > > > > pcm0: unregister: channel pcm0:play:2 busy (pid 965) > > > > And there's no pid 965. > > > > paprika# cat /dev/sndstat > > FreeBSD Audio Driver (newpcm) > > Installed devices: > > pcm0: at io 0xd800 irq 5 (4p/1r/0v channels duplex default) > > > > Any suggestions welcome; in the mean time, I'll just listen to it ding > > away ad naueseum. > > > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > > robert@fledge.watson.org Senior Research Scientist, McAfee Research > > > > As was pointed out, this is probably an interrupt problem. The sound > hardware should have interrupted the driver to say that it was almost > done playing what was in the _ring_ buffer, and the driver should have > responded by either filling the buffer with new data, or turning off the > hardware. Instead, the hardware just kept on doing what it was designed > to do: keep on playing through the ring buffer. The same thing would > have happened if the OS had crashed while a sample was playing. > > The maestro3 driver is growing more stale over time. I no longer have > any hardware to deal with it though. If anyone knows where I can get > an Maestro3 or Allegro-1 PCI card, I'll gladly buy it and fix start > working on the driver again. If you can get your hands on some not-so-old Dell laptops. My Lattitude C400 at work has a Maestro3.