From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: ALSA crash Date: Fri, 19 Jul 2002 20:10:09 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <3D328503.5000705@renta.net> <3D37F5B8.AE18A86B@multitech.co.in> Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <3D37F5B8.AE18A86B@multitech.co.in> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Shaju Abraham Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Fri, 19 Jul 2002 16:49:20 +0530, Shaju Abraham wrote: > > Hi, > Pls check the attached file that is dmesg of a ALSA crash. Can > you pls tell under what conditions this happens? which kernel are you using? is it a modified one? the message appears when the interrupt is generated more lately than expected. so it might be a hardware problem, but not always true. especially onboard chip there could be workaround on the driver side. > Another thing ... in pcm_lib.c , for the funtion snd_pcm_update_hw_ptr. > , there is a comment that "this should be called with interrupts > disabled". Can you tell us who is disabling the interrupts just before > this is called? snd_pcm_update_hw_ptr() is called from either during read/write syscall or tick callback. most likely the former case. anyway it would be nice if you can track down from where it's called. (note that snd_pcm_update_hw_ptr_interrupt() is called from the lowlevel driver's interrupts) > Does spin_lock_irq do that? in most cases, yes. but you don't need take care of that, unless you call it directly from somewhere. Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf