All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yitao Duan <duan@cs.berkeley.edu>
To: Jaroslav Kysela <perex@suse.cz>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Problem with arecord on Audigy 2 NX
Date: Mon, 29 Mar 2004 15:05:52 -0800	[thread overview]
Message-ID: <4068ABD0.18FCFB1F@cs.berkeley.edu> (raw)
In-Reply-To: Pine.LNX.4.58.0403271339440.1836@pnote.perex-int.cz

Thanks for the info, Jaroslav. I upgraded all of the lib, driver, tools, and
utils to 1.0.4rc1. But I got the same results: linux rec command worked fine
but arecord caused Segmentation fault after readi_func was called 3 times
(aplay also worked alright). Any idea what can be happening? Or is there
anybody using the same card (Audigy 2 NX) without problem?

Thanks.

Yitao

Jaroslav Kysela wrote:

> On Fri, 26 Mar 2004, Yitao Duan wrote:
>
> > Hi,
> >
> > I am having trouble recording using Creative Labs Sound Blaster Audigy 2
> > NX. The linux rec program worked fine. But whenever I use arecord (e.g.
> > arecord test.wav), I got Segmentation fault. I pinpointed the problem to
> > the function  pcm_read in aplay.c. Specifically it was the line:
> >
> >  r = readi_func(handle, data, count);
> >
> > that caused the fault. readi_func was called 3 times without problem.
> > But the 4th call will cause the fault. gdb showed that a NULL pointer
> > was encountered in function snd_pcm_rate_grab_next_period: rate->slave
> > was NULL. The following is a stack trace when the fault happened.
> > However, rate->slave was not NULL during the 3 normal readi_func calls
> > and I checked that the handle passed to readi_func was always the same.
> > What could happen that made the pointer NULL for the 4th call? I am
> > running 2.4.21-4.EL kernel and gcc 3.2.3. Any information will be highly
> > appreciated.
>
> Try alsa-lib-1.0.4rc1.
>
>                                                 Jaroslav
>
> -----
> Jaroslav Kysela <perex@suse.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, SuSE Labs



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-03-29 23:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26 23:02 Problem with arecord on Audigy 2 NX Yitao Duan
2004-03-27 12:39 ` Jaroslav Kysela
2004-03-29 23:05   ` Yitao Duan [this message]
2004-03-30  7:08     ` Jaroslav Kysela

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4068ABD0.18FCFB1F@cs.berkeley.edu \
    --to=duan@cs.berkeley.edu \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.