From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>, Hans de Goede <hdegoede@redhat.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: pulseaudio fails to start with kernel 4.11, caused by new snd_hdmi_lpe_audio module)
Date: Mon, 20 Mar 2017 16:09:22 -0700 [thread overview]
Message-ID: <6754b5cd-f6d0-e2e3-0f01-992946ec1b92@linux.intel.com> (raw)
In-Reply-To: <s5h8to0w4fs.wl-tiwai@suse.de>
On 3/20/17 4:52 AM, Takashi Iwai wrote:
> On Mon, 20 Mar 2017 12:42:58 +0100,
> Hans de Goede wrote:
>>
>> Hi,
>>
>> Lately I've been working on fixing various issues people
>> are having with baytrail / cherrytrail devices. One thing
>> I noticed when moving my testing / development to 4.11 is
>> that pulseaudio does not work (it aborts while starting)
>> this seemed to be caused by the new snd_hdmi_lpe_audio
>> module. If I blacklist that all is fine. Any idea what
>> is causing this ?
>
> I noticed it once, too, but I had no time to check further.
> More interestingly, PA works fine when LPE audio is the single driver
> (i.e. blacklist Intel SST instead), too. So it's more likely a bug in
> PA.
>
> What happens when you modprobe LPE audio driver after starting the
> session? If it kills PA, we can debug more easily :)
I've seen this as well, I could get either one of the two but not both,
could this be due to the fact that one set of mixers is configured with
UCM and the other driver isn't configured by UCM?
next prev parent reply other threads:[~2017-03-20 23:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 11:42 pulseaudio fails to start with kernel 4.11, caused by new snd_hdmi_lpe_audio module) Hans de Goede
2017-03-20 11:52 ` Takashi Iwai
2017-03-20 23:09 ` Pierre-Louis Bossart [this message]
2017-03-21 5:40 ` Takashi Iwai
2017-03-21 7:54 ` Arun Raghavan
2017-03-21 8:56 ` [pulseaudio-discuss] " Hans de Goede
2017-03-21 9:04 ` Arun Raghavan
2017-03-21 14:49 ` [pulseaudio-discuss] " Hans de Goede
2017-03-21 15:05 ` Arun Raghavan
2017-03-23 3:16 ` [alsa-devel] " Pierre-Louis Bossart
2017-03-23 8:57 ` [pulseaudio-discuss] " Takashi Iwai
2017-03-24 18:18 ` [alsa-devel] " Tanu Kaskinen
2017-03-24 22:01 ` [pulseaudio-discuss] " Hans de Goede
2017-03-28 20:10 ` [alsa-devel] " Tanu Kaskinen
2017-03-29 5:21 ` Takashi Iwai
2017-03-29 12:59 ` Tanu Kaskinen
2017-03-29 13:06 ` Takashi Iwai
2017-03-29 13:14 ` [pulseaudio-discuss] " Tanu Kaskinen
2017-03-29 13:26 ` Takashi Iwai
2017-03-29 14:40 ` [alsa-devel] " Tanu Kaskinen
2017-03-29 14:51 ` Takashi Iwai
2017-03-30 16:06 ` Tanu Kaskinen
2017-03-30 19:26 ` Takashi Iwai
2017-03-29 13:27 ` Tanu Kaskinen
2017-03-29 13:30 ` [pulseaudio-discuss] " 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=6754b5cd-f6d0-e2e3-0f01-992946ec1b92@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=hdegoede@redhat.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).