On Tue, 21 Mar 2017, at 11:10 AM, Takashi Iwai wrote: > On Tue, 21 Mar 2017 00:09:22 +0100, > Pierre-Louis Bossart wrote: > > > > 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? > > No idea, and I had still no time to check (still processing the > pile of pending mails and other bugs :). Let me add PA guys to Cc. Not sure if anyone here has the hardware and I haven't seen any complaints either -- having a backtrace (or even location of the assert) would be a good start. Cheers, Arun
