mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kevin Puetz <puetzk@puetzk.org>
To: jjluza <jjluza@free.fr>,
	linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@suse.cz>
Subject: Alsa deadlock fix (was Re: 2.6-test8 : alsa hangs my box)
Date: Sun, 26 Oct 2003 11:45:18 -0600	[thread overview]
Message-ID: <200310261145.18537.puetzk@puetzk.org> (raw)

I am seeing this hang also, on a different card, whenever a native alsa and an 
OSS-emulation app collide. No nVidia stuff this time, and not snd_intel8x0 
either, this is w/ a via82xx motherboard's integrated sound. From what little 
one can tell from the sysrq-T backtrace, it looks like a classic deadlock 
(both tasks stick in down(), probably on different mutexes). 

It also looks like it has alreay been fixed (in alsa 0.9.7b) - I think the 
kernel's alsa is approximately equivalent to 0.9.6 these days? So, it looks 
like either some work to port that patch or a wholesale merge of alsa 0.9.8 
would be good before 2.6.0... probably the former given Linus's 
strongly-worded comments with -test9 :-) 

But a deadlock that results in two unkillable state 'D' processes whenever you 
an OSS and an alsa-native app access the soundcard at the same time, which 
happens on both VIA and Intel integrated sound, seems like a hang which might 
meet his criteria of problems which "causes lockups or just basic 
nonworkingness: and this happens on hardware that normal people are expected 
to have". So I figured it's worth asking if someone who already knows what 
the fix consisted of could push it toward Linus ...

             reply	other threads:[~2003-10-26 17:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-26 17:45 Kevin Puetz [this message]
2003-10-26 18:00 ` Alsa deadlock fix Måns Rullgård
2003-10-27  4:00   ` Kevin Puetz

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=200310261145.18537.puetzk@puetzk.org \
    --to=puetzk@puetzk.org \
    --cc=jjluza@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    /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

Powered by JetHome