mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Giuliano Pochini <pochini@shiny.it>
Cc: "F. Heitkamp" <heitkamp@ameritech.net>,
	linux-audio-user@lists.linuxaudio.org,
	alsa-user@lists.sourceforge.net,
	Clemens Ladisch <clemens@ladisch.de>,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Crash 2.6.32.x, Echo 3G, Alsa, SCSI
Date: Tue, 01 Jun 2010 07:37:58 +0200	[thread overview]
Message-ID: <s5heigr8g95.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100531225936.4a9344df@Jay>

At Mon, 31 May 2010 22:59:36 +0200,
Giuliano Pochini wrote:
> 
> On Mon, 31 May 2010 15:05:08 -0400
> "F. Heitkamp" <heitkamp@ameritech.net> wrote:
> 
> > On 02/02/10 17:09, Giuliano Pochini wrote:
> > > On Tue, 02 Feb 2010 16:30:27 +0100
> > > Clemens Ladisch<clemens@ladisch.de>  wrote:
> > >
> > >    
> > >> Frederick V Heitkamp wrote:
> > >>      
> > >>> Repeatable Hard Crash.
> > >>> What else do I need to provide?
> [...]
> > > Signed-off-by: Giuliano Pochini<pochini@shiny.it>
> > >
> > > --- alsa-driver-1.0.22.1/alsa-kernel/pci/echoaudio/echoaudio.c__orig	2010-02-02 22:37:33.000000000 +0100
> > > +++ alsa-driver-1.0.22.1/alsa-kernel/pci/echoaudio/echoaudio.c	2010-02-02 22:44:03.000000000 +0100
> > > @@ -1821,7 +1821,9 @@ static irqreturn_t snd_echo_interrupt(in
> > >   	/* The hardware doesn't tell us which substream caused the irq,
> > >   	thus we have to check all running substreams. */
> > >   	for (ss = 0; ss<  DSP_MAXPIPES; ss++) {
> > > -		if ((substream = chip->substream[ss])) {
> > > +		substream = chip->substream[ss];
> > > +		if (substream&&  ((struct audiopipe *)substream->runtime->
> > > +				private_data)->state == PIPE_STATE_STARTED) {
> > >   			period = pcm_pointer(substream) /
> > >   				substream->runtime->period_size;
> > >   			if (period != chip->last_period[ss]) {
> > >
> > >
> > >    
> > I've tried some newer kernels.  Still having problems with the echo 3G.  
> > This is kernel version:
> > 2.6.32.13.  The above patches posted to the linux kernel list seemed to 
> > get rid of the crashes, but evidently did not go into the main kernel tree.
> 
> Indeed. I've just checked 2.6.33 and the patch isn't there. It's in 2.6.34.
> 
> If you need 2.6.32.13 you can apply the above patch to the kernel tree or
> download ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.23.tar.bz2,
> otherwise just use the latest kernel.

Care to send the patch to stable kernel (with the upstream commit id)?


thanks,

Takashi

  reply	other threads:[~2010-06-01  5:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 14:21 Frederick V Heitkamp
2010-02-02 15:30 ` [alsa-devel] " Clemens Ladisch
2010-02-02 16:02   ` Giuliano Pochini
2010-02-02 22:09   ` Giuliano Pochini
2010-02-03  2:53     ` Frederick V Heitkamp
2010-05-31 19:05     ` F. Heitkamp
2010-05-31 20:59       ` Giuliano Pochini
2010-06-01  5:37         ` Takashi Iwai [this message]
2010-06-01 12:25         ` [Alsa-user] " F. Heitkamp
2010-06-02 22:08           ` Giuliano Pochini
2010-06-17 12:11             ` F. Heitkamp
2010-06-18 11:55               ` Giuliano Pochini

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=s5heigr8g95.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=clemens@ladisch.de \
    --cc=heitkamp@ameritech.net \
    --cc=linux-audio-user@lists.linuxaudio.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pochini@shiny.it \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®