From: Takashi Iwai <tiwai@suse.de>
To: Shaju Abraham <shaju@multitech.co.in>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA crash
Date: Fri, 19 Jul 2002 20:10:09 +0200 [thread overview]
Message-ID: <s5h7kjrr3lq.wl@alsa2.suse.de> (raw)
In-Reply-To: <3D37F5B8.AE18A86B@multitech.co.in>
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
prev parent reply other threads:[~2002-07-19 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 8:17 /proc/asound/meminfo Mark Constable
2002-07-15 10:02 ` /proc/asound/meminfo Takashi Iwai
2002-07-19 11:19 ` ALSA crash Shaju Abraham
2002-07-19 12:02 ` Paul Davis
2002-07-19 18:10 ` Takashi Iwai [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=s5h7kjrr3lq.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=shaju@multitech.co.in \
/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