From: Guilherme <grlongo.ireland@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>, alsa-devel@alsa-project.org
Subject: Re: sound device is buzy to run pcm.c
Date: Wed, 17 Jun 2009 11:59:11 -0300 [thread overview]
Message-ID: <4A3904BF.5090101@gmail.com> (raw)
In-Reply-To: <75b66ecd0906161944q40f471fdiae23c3290c866e85@mail.gmail.com>
Lee, I noticed that and I killed the process.
After I have it killed, the program gimme segfault.....!
;O( Ill check it in another machine to see what happens!
Tks!
-------------------
Guilherme Longo
Dept. Eng. da Computação
Unaerp
Linux User - #484927
*Before Asking
http://www.istf.com.br/?page=perguntas
!- I'd rather die on my feet than live on my knees -!
Lee Revell wrote:
> On Sun, Jun 14, 2009 at 11:11 PM, Guilherme Raymo
> Longo<grlongo.ireland@gmail.com> wrote:
>
>> I tried to check if the device is really buzy:
>>
>> root@lap:/home/guilherme/Experimentos# lsof |grep snd
>> lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system */
>> home/guilherme/*.gvfs
>> Output information may be incomplete.
>> esd 5433 guilherme mem CHR 116,16 6947
>> /dev/snd/pcmC0D0p
>> esd 5433 guilherme 5r CHR 116,33 6787
>> /dev/snd/timer
>> esd 5433 guilherme 6w CHR 116,16 6947
>> /dev/snd/pcmC0D0p
>> esd 5433 guilherme 7r CHR 116,0 6987
>> /dev/snd/controlC0
>>
>> and it seems to be ok.
>>
>
> Of course it's busy, esd has it open.
>
> Lee
>
>
prev parent reply other threads:[~2009-06-17 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 3:11 sound device is buzy to run pcm.c Guilherme Raymo Longo
2009-06-17 2:44 ` Lee Revell
2009-06-17 14:59 ` Guilherme [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=4A3904BF.5090101@gmail.com \
--to=grlongo.ireland@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=rlrevell@joe-job.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