/proc/asound/meminfo
Is this still a valid /proc/asound entry ?
/proc/asound/meminfo (RO)
memory usage information
--markc
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
At Mon, 15 Jul 2002 18:17:07 +1000,
Quoted 5 lines · Mark Constable
Is this still a valid
/proc/asoundentry ?
/proc/asound/meminfo(RO)
memory usage information
oh, i forgot to mention:
this proc file appears only when you built the alsa drivers with memory debug (or full) option.
the file shows the currently allocated memories on kernel space.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
ALSA crash
Hi,
Pls check the attached file that is dmesg of a ALSA crash. Can
you pls tell under what conditions this happens?
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?
Does spin_lock_irq do that?
We are using RedHat 7.1 linux on i810 motherboard and the latest version of ALSA 0.9.0.
Shaju Abraham.
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -46, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -4, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -4, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -6, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -6, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -56, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -2, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -6, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -4, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -68, max jitter = 4480): wrong interrupt acknowledge?
ALSA ../alsa-kernel/core/pcm_lib.c:188: Unexpected hw_pointer value (stream = 0, delta: -4, max jitter = 4480): wrong interrupt acknowledge?
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Re: ALSA crash
Quoted 10 lines
Hi,
Pls check the attached file that is dmesg of a ALSA crash. Can
you pls tell under what conditions this happens?Another thing ... in
pcm_lib.c, for the funtionsnd_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?Does
spin_lock_irqdo that?
sort of. but the main and usually only place where snd_pcm_update_hw_ptr is called is from the interrupt handler for the audio interface, which is called with interrupts disabled by the kernel.
--p
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Re: ALSA crash
In reply to Shaju AbrahamAt Fri, 19 Jul 2002 16:49:20 +0530,
Quoted 4 lines · Shaju Abraham
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.
Quoted 4 lines
Another thing ... in
pcm_lib.c, for the funtionsnd_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)
Quoted 1 line
Does
spin_lock_irqdo 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