From: Takashi Iwai Subject: Re: ALSA OSS Emulation - Read - EAGAIN Errors Date: Thu, 31 Jul 2008 12:04:28 +0200 Message-ID: References: <233031.41599.qm@web59615.mail.ac4.yahoo.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.suse.de (cantor.suse.de [195.135.220.2]) by alsa0.perex.cz (Postfix) with ESMTP id BD3992458F for ; Thu, 31 Jul 2008 12:04:28 +0200 (CEST) In-Reply-To: <233031.41599.qm@web59615.mail.ac4.yahoo.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Rahul Iyer Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Wed, 30 Jul 2008 08:20:09 -0700 (PDT), Rahul Iyer wrote: > > Hi ALSA Developers > > > I have a full duplex voice application, that records voice and sends > (over a network) as well as receives and plays voice. OSS APIs are used > to capture and play voice samples. > > The voice quality is noticeably poor in SUSE 10. After further > investigation, I see most of the 'read' system calls fail with EAGAIN > (resource unavailable) error. EAGAIN is no fatal error but means that samples are not available for read when the stream is opened in non-blocking mode. If it happens so often, it's likely a parameter mismatch. For example, the read period size apps expected doesn't match with the size actually set. It's better to create a small test-case first then analyze the problem with it. Takashi