Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: User for realtime audio <audiodev@ind.RWTH-Aachen.DE>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Terratec EWS88MT
Date: Tue, 22 Oct 2002 12:39:36 +0200	[thread overview]
Message-ID: <s5hptu23ggn.wl@alsa2.suse.de> (raw)
In-Reply-To: <3DB50238.5000103@ind.rwth-aachen.de>

Hi,

At Tue, 22 Oct 2002 09:46:00 +0200,
User for realtime audio wrote:
> 
> I am running kernels 2.4.16 with low latency patches and the RTC patch from
> alsa-package-rc3
> and 2.4.18 without any patches alternatively. The alsa-package was rc-3 and is now the
> current
> CVS-version. In all cases envy24control and amixer contents lead to the system lock
> (amixer without contents works fine!)
> 
> I have started "strace envy24control" which let me know that
> 
> ioctl(4, 0xc245512, 0xbfffedb0)
> 
> is the instruction that causes the system lock. Multiple ioctls with only the third
> argument differing
> returned 0 just before the system lock.
> 
> When calling amixer contents, the last message printed is:
> 
> numid=103, iface=mixer, name='Input Sensitivity Switch', index=1
>     ; TYPE=enumerated, access=rw---, values=1, items=2
>     ; Item #0 ='+4dBu'
>     ; Item #1 = '-10dBV'

thanks for spotting this!
there was actually a deadlock in this part.

fixed now on cvs.  please give a try.
(please note that on the cvs snd_ prefix is removed.)


ciao,

Takashi


-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future of 
Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) 
program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
http://www.sun.com/javavote

      reply	other threads:[~2002-10-22 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 14:20 Terratec EWS88MT User for realtime audio
2002-10-21 14:35 ` Takashi Iwai
2002-10-22  7:46   ` User for realtime audio
2002-10-22 10:39     ` 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=s5hptu23ggn.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=audiodev@ind.RWTH-Aachen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox