From mboxrd@z Thu Jan  1 00:00:00 1970
From: Takashi Iwai <tiwai@suse.de>
Subject: Re: Backported sbxfi driver (UNTESTED!)
Date: Fri, 17 Oct 2008 08:17:17 +0200
Message-ID: <s5hbpxj6902.wl%tiwai@suse.de>
References: <s5hy70xsl46.wl%tiwai@suse.de>
	<loom.20081016T120322-319@post.gmane.org>
	<s5h8wso3ejg.wl%tiwai@suse.de>
	<48F739F4.5070303@nostalgicnetworxx.org>
	<48F74344.4090509@gmail.com> <s5hvdvs1wig.wl%tiwai@suse.de>
	<48F74C91.7040708@gmail.com> <s5hprm01v3g.wl%tiwai@suse.de>
	<48F75284.1040901@gmail.com> <s5hljwo1u01.wl%tiwai@suse.de>
	<48F75700.5060102@gmail.com> <s5hfxmw1syu.wl%tiwai@suse.de>
	<48F75892.8000209@gmail.com> <s5hbpxk1shh.wl%tiwai@suse.de>
	<48F7855F.6060806@gmail.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: <alsa-devel-bounces@alsa-project.org>
Received: from mx2.suse.de (mx2.suse.de [195.135.220.15])
	by alsa0.perex.cz (Postfix) with ESMTP id 47644103827
	for <alsa-devel@alsa-project.org>;
	Fri, 17 Oct 2008 08:17:35 +0200 (CEST)
In-Reply-To: <48F7855F.6060806@gmail.com>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Sender: alsa-devel-bounces@alsa-project.org
Errors-To: alsa-devel-bounces@alsa-project.org
To: The Source <thesourcehim@gmail.com>
Cc: alsa-devel@alsa-project.org
List-Id: alsa-devel@alsa-project.org

At Thu, 16 Oct 2008 22:18:07 +0400,
The Source wrote:
> 
> >> Ok. OpenAL with alsa also seem to cause problems.
> >>     
> >
> > In both cases, check the period_size and buffer_size values (shown in
> > the kernel message, or /proc/asound/card0/pcm0p/sub0/hw_params).
> > And, try to aplay with these parameters, whether you get the similar
> > problem.
> >
> > 	% aplay -v --period-size=xxx --buffer-size=yyy foo.wav
> >
> >
> > Takashi
> >
> >   
> I'm sorry, but any attemp to play file with ossplay results in complete 
> system hang with error:
> unable to handle NULL ponter dereference at address 
> 0000000000000008.....(hang, no more output).
> I tried many wav formats. So I can't get error log or period and buffer 
> sizes, sorry.

Can anyone confirm to reproduce Oops with OSS apps (ossplay)?

I'm wondering whether this has anything to do with the capture.
Can you record the sound, and change the capture mixer element properly?


thanks,

Takashi