All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Sjostrand <gorm@cucumelo.org>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: anybody else OK with current CVS *and* SMP?
Date: Thu, 07 Aug 2003 00:20:23 +0200	[thread overview]
Message-ID: <3F317F27.7010702@cucumelo.org> (raw)
In-Reply-To: 200308051417.h75EHwpr020319@localhost.localdomain

>
>
>i am having a repeated problem with system lockups using current CVS
>with JACK running SCHED_FIFO on an SMP system, with the Planet's
>2.4.21 kernel.
>
>can anyone report that a similar configuration is working for them?
>there is no way to diagnose the situation, because the kernel hangs
>totally and completely, and its not possible to get the output from
>either an oops or the magic-request key(s).
>
>it seems to be less of a problem when JACK is running without
>SCHED_FIFO. 
>  
>
A couple of month agoo I've tried to upgrade the ALSA CVS, and I 
remember that I got
almost exactly the same sympton that you are describing.

Sometimes when running JACK without X, the SysRQ key works, however
I did not get any useful information from it, I did not get any 
interactive response
from the developer list, and I've been very lasy ....

Since that I'm using a very old ALSA CVS version from May 17, that seems
to work fine with SMP.

/Benny



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

  parent reply	other threads:[~2003-08-06 22:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 14:17 anybody else OK with current CVS *and* SMP? Paul Davis
2003-08-05 20:37 ` Antti Boman
2003-08-06 11:24   ` Takashi Iwai
2003-08-06 12:28     ` Antti Boman
2003-08-07  8:43   ` Giuliano Pochini
2003-08-06 14:05 ` John Anderson
2003-08-06 14:39   ` John Anderson
2003-08-06 14:48     ` Takashi Iwai
2003-08-06 15:04       ` John Anderson
2003-08-06 15:13         ` Paul Davis
2003-08-06 15:31           ` Takashi Iwai
2003-08-06 15:34             ` Paul Davis
2003-08-06 16:11           ` John Anderson
2003-08-07  7:20           ` Antti Boman
2003-08-07  8:18             ` Chris Rankin
2003-08-07 18:25           ` Fernando Pablo Lopez-Lezcano
2003-08-07 18:30             ` Paul Davis
2003-08-07 18:40               ` Fernando Pablo Lopez-Lezcano
2003-08-07 19:19               ` Steve Harris
2003-08-06 22:20 ` Benny Sjostrand [this message]
2003-08-07  6:41 ` Kai Vehmanen
2003-08-07  6:51   ` Jeremy Hall
2003-08-07  7:05     ` Kai Vehmanen
2003-08-07 11:07       ` Jeremy Hall
2003-08-07 13:17         ` Paul Davis
2003-08-07 13:22   ` Paul Davis
2003-08-11 15:44     ` Takashi Iwai

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=3F317F27.7010702@cucumelo.org \
    --to=gorm@cucumelo.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --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.