From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
"alsa-devel@lists.sourceforge.net"
<alsa-devel@lists.sourceforge.net>
Subject: Re: [patch] pcm-record (was cs46xx record (Thinkpad A22) => deadlock)
Date: Thu, 31 Oct 2002 11:32:47 +0100 [thread overview]
Message-ID: <3DC106CF.3020301@gmx.at> (raw)
In-Reply-To: Pine.LNX.4.33.0210302132490.611-100000@pnote.perex-int.cz
Jaroslav Kysela wrote:
> On Wed, 30 Oct 2002, Takashi Iwai wrote:
>>At Tue, 29 Oct 2002 15:07:41 +0100,
>>Wilfried Weissmann wrote:
>>>[1 <text/plain; us-ascii (7bit)>]
>>>I dug a little around in the code. The infinitive loop was caused by
>>>being stuck in DRAINING mode. snd_pcm_lib_read1() returns -EPIPE in this
>>>case (pcm_lib.c: 2146). Then we return to snd_pcm_oss_read3() which
>>>continues to call this function until jdoomsday (= SysRq+b). I changed
>>>the code to call snd_pcm_update_hw_ptr() before that. The patch is
>>>attached. It *seems* to fix it. You want to have a _real_ close look at
>>>that if you want to apply the patch, as it is just a shot in the dark.
>>>At least I know now that the problem is (I figured it out by inserting
>>>printk).
>>
>>looks correct. applied to cvs now.
>
>
> It's wrong. I reverted the change and included new updated code for the
> OSS emulation.
I just tested the new patch. It works perfectly. Thanks all.
bye,
Wilfried
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
prev parent reply other threads:[~2002-10-31 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 14:07 [patch] pcm-record (was cs46xx record (Thinkpad A22) => deadlock) Wilfried Weissmann
2002-10-30 18:12 ` Takashi Iwai
2002-10-30 20:33 ` Jaroslav Kysela
2002-10-31 10:32 ` Wilfried Weissmann [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=3DC106CF.3020301@gmx.at \
--to=wilfried.weissmann@gmx.at \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=tiwai@suse.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 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.