From: Marco Trillo <martri@arantia.com>
To: Alexander Shashkevych <alex@stunpix.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: pulseaudio makes system unstable
Date: Tue, 25 Nov 2014 17:25:51 +0100 [thread overview]
Message-ID: <5474AD8F.6020204@arantia.com> (raw)
In-Reply-To: <CAE6DSAESJmEOxh6n7aULFGQFOXHncXmGCtZpQB8bmjZXD+tjbg@mail.gmail.com>
Hi,
On 11/25/2014 05:05 PM, Alexander Shashkevych wrote:
>> Which audio device are you using? The HDMI port (imx-hdmi-soc-audio) or the
>> analog port (sgtl5000) on the Wandboard? If you are indeed using the HDMI
>> audio, could you try using the analog audio and see if the problem persists?
>>
>> I reproduced the 'Illegal instruction' crashes you mention when using HDMI
>> audio -- not only with `pulsesink' but also with `alsasink' depending on
>> other unrelated particularities of the test-- but the problem disappeared as
>> soon as I switched to the sgtl5000 audio.
> I've tried to use different pulse sinks and I see that it behaves a
> bit differently, but still unstable. Sometimes pavucontrol closes
> unexpectedly, sometimes desktop closes, sometimes pulse server stops
> and once pulse server stops, gstreamer can't connect again to newly
> started instance of server and so on. Very strange and unpredictable.
Yeah, I understand. I also remember these issues with `pulseaudio' when
I did my tests. ISTR that starting the daemon with `--exit-idle-time=-1'
and `--allow-exit=false' avoided the daemon to stop as you mention.
However I think these issues are not related to the `Illegal
instruction' crashes. Did these crashes still occur when using the
analog device as a sink? For me, these crashes were linked to the HDMI
audio output device.
Kind regards,
Marco
next prev parent reply other threads:[~2014-11-25 16:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 12:12 pulseaudio makes system unstable Alexander Shashkevych
2014-11-24 13:29 ` Marco Trillo
2014-11-25 16:05 ` Alexander Shashkevych
2014-11-25 16:21 ` Daiane Angolini
2014-11-25 16:52 ` Alexander Shashkevych
2014-11-25 18:42 ` Alexander Shashkevych
2014-11-28 15:23 ` Otavio Salvador
2014-11-28 17:34 ` Alexander Shashkevych
2014-11-28 18:22 ` Otavio Salvador
2014-11-29 10:46 ` Alexander Shashkevych
2014-11-29 13:02 ` Otavio Salvador
2014-11-25 16:25 ` Marco Trillo [this message]
2014-11-25 17:06 ` Alexander Shashkevych
2014-11-24 20:03 ` Status of imx28evk recipes/images Simone
2014-11-25 10:58 ` Daiane Angolini
2014-11-25 11:02 ` Otavio Salvador
2014-11-25 13:24 ` Simone
2014-11-25 14:44 ` Daiane Angolini
2014-11-25 19:47 ` Simone
2014-11-27 11:55 ` Daiane Angolini
2014-11-27 12:31 ` Simone
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=5474AD8F.6020204@arantia.com \
--to=martri@arantia.com \
--cc=alex@stunpix.com \
--cc=meta-freescale@yoctoproject.org \
/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.