From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id ED0CBE008D9; Tue, 25 Nov 2014 08:26:01 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mailext0.televes.com (mailext0.televes.com [212.163.42.140]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9F79EE0084E for ; Tue, 25 Nov 2014 08:25:55 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailext0.televes.com (Postfix) with ESMTP id 899709A3FAD; Tue, 25 Nov 2014 17:25:53 +0100 (CET) X-Virus-Scanned: by amavisd-new at mailext0.televes.com Received: from mailext0.televes.com ([127.0.0.1]) by localhost (mailext0.televes.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a3Wl-v8+RR1P; Tue, 25 Nov 2014 17:25:53 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mailext0.televes.com (Postfix) with ESMTP id 521F39A4073; Tue, 25 Nov 2014 17:25:53 +0100 (CET) Received: from tves0.televes.com (tvesbackup0 [212.163.42.137]) by mailext0.televes.com (Postfix) with ESMTP id 3D8229A3FAD; Tue, 25 Nov 2014 17:25:53 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by tves0.televes.com (Postfix) with ESMTP id DDA94F024EDD9; Tue, 25 Nov 2014 17:25:52 +0100 (CET) Received: from arantia1.arantia.com (ARANTIA0.televes.com [192.168.178.2]) by tves0.televes.com (Postfix) with ESMTP id D2A41F024EDD8; Tue, 25 Nov 2014 17:25:52 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by arantia1.arantia.com (Postfix) with ESMTP id B2945161C224; Tue, 25 Nov 2014 17:25:52 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by arantia1.arantia.com (Postfix) with ESMTP id 8D96E16216D2; Tue, 25 Nov 2014 17:25:52 +0100 (CET) Received: from arantia1.arantia.com ([127.0.0.1]) by localhost (arantia0 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04634-07; Tue, 25 Nov 2014 17:25:51 +0100 (CET) Received: from [192.168.178.108] (unknown [192.168.178.108]) by arantia1.arantia.com (Postfix) with ESMTP id 301A7161C224; Tue, 25 Nov 2014 17:25:51 +0100 (CET) Message-ID: <5474AD8F.6020204@arantia.com> Date: Tue, 25 Nov 2014 17:25:51 +0100 From: Marco Trillo User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Alexander Shashkevych References: <547332AA.40906@arantia.com> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: pulseaudio makes system unstable X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2014 16:26:02 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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