From owner-freebsd-multimedia Sun Jul 13 19:14:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA21984 for multimedia-outgoing; Sun, 13 Jul 1997 19:14:35 -0700 (PDT) Received: from elch.heim4.tu-clausthal.de (100@elch.heim4.tu-clausthal.de [139.174.244.250]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA21979 for ; Sun, 13 Jul 1997 19:14:32 -0700 (PDT) Received: (from olli@localhost) by elch.heim4.tu-clausthal.de (8.8.5/8.8.5) id EAA16083 for multimedia@FreeBSD.ORG; Mon, 14 Jul 1997 04:14:29 +0200 (MET DST) Message-Id: <199707140214.EAA16083@elch.heim4.tu-clausthal.de> Subject: Re: guspnp9: /dev/dsp close() hangs To: multimedia@FreeBSD.ORG Date: Mon, 14 Jul 1997 04:14:29 +0200 (MET DST) In-Reply-To: <19970713191453.21533@ct.picker.com> from "Randall Hopper" at Jul 13, 97 07:14:53 pm From: oliver.fromme@heim3.tu-clausthal.de (Oliver Fromme) X-Mailer: ELM [version 2.4 PL24 PGP6] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-multimedia@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Maybe this information could be useful in some way... Randall Hopper wrote: > [...] > > mpg123 things.mp2 > > -----> APP STARTUP PRINTS: > start sb_reset_dsp > done RESET 1 > done tenmicrosec > done RESET 0 > isa_dmastart: channel 5 busy > > -----> THEN WHEN I CTRL-C, I ALWAYS SEE THIS: > dmabuf 2 > dmabuf 1 > > -----> IF THE /dev/dsp close() DIDN'T HANG, THAT'S IT. > > -----> BUT IF THE close() HUNG, I SEE THIS LINE AGAIN AND AGAIN, PRINTING > -----> ONCE EVERY 10 SECONDS: > dmabuf 1 Using the soundrivers of 2.2.2 (Vox 2.9, I think) with an AWE32, I also experience hangs sometimes when /dev/dsp is closed, BUT only for about 10 seconds. It never blocks forever (maybe it checks for a timeout). To be honest, I first suspected a bug in mpg123, but I've looked at the respective parts of the code for days, and I haven't been able to spot a bug... Regards Oliver PS: I just released mpg123 0.59k, see http://mpg.123.org/ Doesn't fix the block-on-close problem though, of course. PPS: In case you didn't notice, I'm not that much familiar with all that sound driver stuff. I assume it's not possible to install those newer "guspnp" drivers in 2.2.2, is it? Stability is an absolute requirement for me, so I don't want to install 3.0-current. -- Oliver Fromme, Leibnizstr. 18-61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)