From owner-freebsd-stable Wed Oct 14 15:22:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06834 for freebsd-stable-outgoing; Wed, 14 Oct 1998 15:22:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from B1FF.nas.nasa.gov (b1ff.nas.nasa.gov [129.99.34.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06823 for ; Wed, 14 Oct 1998 15:22:22 -0700 (PDT) (envelope-from rone@B1FF.nas.nasa.gov) Received: (from rone@localhost) by B1FF.nas.nasa.gov (8.8.8/8.8.8) id PAA00592 for stable@freebsd.org; Wed, 14 Oct 1998 15:22:05 -0700 (PDT) (envelope-from rone) From: Ron Echeverri Message-Id: <199810142222.PAA00592@B1FF.nas.nasa.gov> Subject: CPU halts using mpg123 and OSS To: stable@FreeBSD.ORG Date: Wed, 14 Oct 1998 15:22:02 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running a kernel that has no Voxware stuff in it (as prescribed by the OSS docs). Everything seems to run OK, but when running mpg123, whenever it tries to come back to a shell prompt (if i suspend or interrupt the process, or if i run it in the background, or if it exits normally after the track ends), the CPU halts. I ktraced the process and let it run normally, dumped the trace, and got 64 megs of normal-looking stuff until the end: 312 mpg123 RET read 414/0x19e 312 mpg123 CALL read(0x3,0xefbfdb0c,0x4) 312 mpg123 GIO fd 3 read 4 bytes "\M^?\M It just stops right there. Where should i look to first? Should i bug 4Front first, upgrade my tcsh, or bug the mpg123 maintainer? thanks rone -- Ron Echeverri Numerical Aerodynamic Simulation Facility DSS/Usenet Administrator NASA Ames Research Center Internet Sysop Mountain View, CA x42771 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message