Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Chris Rankin <rankincj@yahoo.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA-CVS: Unbreakable "sfxload" process
Date: Mon, 17 Feb 2003 18:38:39 +0100	[thread overview]
Message-ID: <s5hr8a6hko0.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030215000815.36420.qmail@web40612.mail.yahoo.com>

At Sat, 15 Feb 2003 00:08:15 +0000 (GMT),
Chris Rankin wrote:
> 
> Hi,
> 
> I have just tried loading a sound-font file into my SB
> Live! and ended up needing to reboot my machine when
> the sfxload program grabbed hold of the CPU and
> wouldn't give it back! Fortunately the machine is SMP,
> and so I was able to shutdown cleanly using the other
> one.
> 
> I think the problem happened because I was trying to
> play a MID file at the time using:
> 
> $ pmidi -p 65:0 <file>
> 
> and didn't break this process before trying to load
> the sound-font. Note also that the sfxload program
> uses /dev/sequencer and so the OSS emulation modules
> are also implicated.
> 
> And the reason I think that this is a kernel problem
> is that the sfxload process survived repeated "kill
> -9" attempts by root... ;-).

hmm, i'm afraid that it's again because of damn kernel memory
allocator...
but, it could be a mutex deadlock of the emu10k1 driver, of course.
i'll take a look tomorrow.


ciao,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      reply	other threads:[~2003-02-17 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-15  0:08 ALSA-CVS: Unbreakable "sfxload" process Chris Rankin
2003-02-17 17:38 ` 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=s5hr8a6hko0.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rankincj@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox