/proc/asound/meminfo

All of lore.kernel.org
 help / color / mirror / Atom feed

* /proc/asound/meminfo
@ 2002-07-15  8:17 Mark Constable
  2002-07-15 10:02 ` /proc/asound/meminfo Takashi Iwai
  0 siblings, 1 reply; 5+ messages in thread
From: Mark Constable @ 2002-07-15  8:17 UTC (permalink / raw)
  To: alsa-devel

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: /proc/asound/meminfo
  2002-07-15  8:17 /proc/asound/meminfo Mark Constable
@ 2002-07-15 10:02 ` Takashi Iwai
  2002-07-19 11:19   ` ALSA crash Shaju Abraham
  0 siblings, 1 reply; 5+ messages in thread
From: Takashi Iwai @ 2002-07-15 10:02 UTC (permalink / raw)
  To: Mark Constable; +Cc: alsa-devel

At Mon, 15 Jul 2002 18:17:07 +1000,
Mark Constable wrote:
> 
> Is this still a valid /proc/asound entry ?
> 
> /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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* ALSA crash
  2002-07-15 10:02 ` /proc/asound/meminfo Takashi Iwai
@ 2002-07-19 11:19   ` Shaju Abraham
  2002-07-19 12:02     ` Paul Davis
  2002-07-19 18:10     ` Takashi Iwai
  0 siblings, 2 replies; 5+ messages in thread
From: Shaju Abraham @ 2002-07-19 11:19 UTC (permalink / raw)
  To: Takashi Iwai; +Cc: alsa-devel

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: ALSA crash
  2002-07-19 11:19   ` ALSA crash Shaju Abraham
@ 2002-07-19 12:02     ` Paul Davis
  2002-07-19 18:10     ` Takashi Iwai
  1 sibling, 0 replies; 5+ messages in thread
From: Paul Davis @ 2002-07-19 12:02 UTC (permalink / raw)
  To: Shaju Abraham; +Cc: Takashi Iwai, alsa-devel

>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?

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: ALSA crash
  2002-07-19 11:19   ` ALSA crash Shaju Abraham
  2002-07-19 12:02     ` Paul Davis
@ 2002-07-19 18:10     ` Takashi Iwai
  1 sibling, 0 replies; 5+ messages in thread
From: Takashi Iwai @ 2002-07-19 18:10 UTC (permalink / raw)
  To: Shaju Abraham; +Cc: alsa-devel

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2002-07-19 18:10 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.