All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Arthur Peters <amp@singingwizard.org>,
	Alsa dev list <alsa-devel@lists.sourceforge.net>
Subject: Re: ALSA + jack + xrun = kernel crash
Date: Mon, 19 May 2003 18:10:02 +0200	[thread overview]
Message-ID: <s5hwugmdijp.wl@alsa2.suse.de> (raw)
In-Reply-To: <E19H0hA-0002q5-00@sc8-sf-list1.sourceforge.net>

At Sat, 17 May 2003 08:27:29 -0400,
Paul Davis wrote:
> 
> >Hello, I am experiencing a reletivly hard crash (SysRq works but SysRq-B
> >prints a message saying it will reboot then doesn't). The crash happens
>   [ ... ]
> >My hardware is:
> >Dual PIII 1Ghz with 512M RAM on a Tyan MB.
>   [ .... ]
> >My software is:
> >ALSA drivers 0.9.3a or current CVS
> 
> current CVS (and presumably 0.9.3a) has a severe bug with SMP
> systems. i reported it last week, along with as much output as i could
> get from my machine when it locked up. nobody has been able to do
> anything about it since then.
> 
> you will need to back to the cvs snapshot of april 27th to get a
> working version for SMP systems.
> 
> jaroslav or takashi - any ideas about fixing this?

it's likely spin dead locks, but it's difficult to guess where this
happens.

after auditing the new codes, i fixed some possible dead locks.
most of the fixed places, however, happen in suspend/resume
conditions or timeout after 10sec, so this unlikely fixes your case.


could you check whether snd_pcm_stream_linked() returns really only
zero?  if yes, the code path shouldn't include the complicated locks
in snd_pcm_action_group(), and it will narrow the possible bugggy
points much...


ciao,

Takashi


-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, 
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge

  parent reply	other threads:[~2003-05-19 16:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17  1:54 ALSA + jack + xrun = kernel crash Arthur Peters
2003-05-17 12:27 ` Paul Davis
2003-05-17 12:47   ` Jaroslav Kysela
2003-05-17 20:48     ` Arthur Peters
2003-05-19 16:10   ` Takashi Iwai [this message]
2003-05-19 16:38     ` Paul Davis
2003-05-19 19:16       ` Benny Sjostrand
2003-05-20  8:46       ` Takashi Iwai
2003-05-21  0:32         ` Pieter Palmers
2003-05-21 10:33           ` Takashi Iwai
2003-05-21 11:35             ` Jaroslav Kysela
2003-05-21 11:49               ` Takashi Iwai
2003-05-21 12:54                 ` Jaroslav Kysela
     [not found]                 ` <3ECBCF5B.2020807@esat.kuleuven.ac.be>
2003-05-21 23:08                   ` Pieter Palmers
2003-05-21 23:50                     ` Tarragon Allen
2003-05-22  1:20                       ` Paul Davis
2003-05-17 20:57 ` Benny Sjostrand
2003-05-17 21:38   ` Jaroslav Kysela

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=s5hwugmdijp.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=amp@singingwizard.org \
    --cc=paul@linuxaudiosystems.com \
    /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.