All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ted T. Logan" <tedtheologian@gmail.com>
To: The Source <thesourcehim@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: snd-ctxfi oops
Date: Wed, 17 Jun 2009 19:17:41 -0500	[thread overview]
Message-ID: <1245284261.3419.0.camel@localhost.localdomain> (raw)
In-Reply-To: <4A38EAF5.8030808@gmail.com>

I upgraded to this new snapshot and have the same click every 1.5
seconds on every single application with my x-fi.

I'm just confused as to why this didn't occur at all with the old
driver, as in, was something strange introduced?

On Wed, 2009-06-17 at 17:09 +0400, The Source wrote:

> On 15.06.2009 17:01, Takashi Iwai wrote:
> > At Mon, 15 Jun 2009 15:00:03 +0200,
> > I wrote:
> >    
> >> At Mon, 15 Jun 2009 16:59:53 +0400,
> >> The Source wrote:
> >>      
> >>> On 15.06.2009 16:56, Takashi Iwai wrote:
> >>>        
> >>>> At Sat, 13 Jun 2009 10:07:49 +0200,
> >>>> I wrote:
> >>>>
> >>>>          
> >>>>>
> >>>>>            
> >>>>>> Tested the patch more. Really no oopses. Instead of them I get rare
> >>>>>> system lockups.
> >>>>>>
> >>>>>>              
> >>>>> In which situation, exactly?
> >>>>> Could you check whether it happens with use_system_timer=1 module
> >>>>> option, too?
> >>>>>
> >>>>>            
> >>>> Or try the very latest alsa-driver-snapshot (not daily tarball).
> >>>> I fixed a deadlock issue in cttimer.c now.
> >>>>
> >>>>
> >>>> thanks,
> >>>>
> >>>> Takashi
> >>>>
> >>>>
> >>>>          
> >>> Should I apply that patch to this snapshot?
> >>>        
> >> Which patch do you mean?
> >> Just grab the latest alsa-driver-snapshot.tar.gz from
> >>      ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/
> >>      
> > Also, check alsa-driver/alsa-kernel/HEAD whether the commit
> >     8dca419721d188bfee5f19fad45275856c619a5c
> >       ALSA: ctxfi - Fix deadlock with xfi-timer
> > is included.
> >
> >
> > Takashi
> >
> >    
> Tested the driver and it's fine so far. No craches with any application 
> including Doom 3, which caused system lockups often with earlier 
> versions of the driver.
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2009-06-18  0:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  3:52 snd-ctxfi oops The Source
2009-06-12  7:20 ` Takashi Iwai
     [not found]   ` <4A329D02.8070202@gmail.com>
2009-06-13  6:05     ` The Source
2009-06-13  8:07       ` Takashi Iwai
2009-06-15 12:56         ` Takashi Iwai
     [not found]           ` <4A3645C9.40804@gmail.com>
     [not found]             ` <s5hvdmxejos.wl%tiwai@suse.de>
     [not found]               ` <s5htz2hejmx.wl%tiwai@suse.de>
2009-06-17 13:09                 ` The Source
2009-06-18  0:17                   ` Ted T. Logan [this message]

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=1245284261.3419.0.camel@localhost.localdomain \
    --to=tedtheologian@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=thesourcehim@gmail.com \
    --cc=tiwai@suse.de \
    /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.