All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Raghavan <arun@arunraghavan.net>
To: Takashi Iwai <tiwai@suse.de>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	alsa-devel@alsa-project.org,
	pulseaudio-discuss@lists.freedesktop.org
Subject: Re: pulseaudio fails to start with kernel 4.11, caused by new snd_hdmi_lpe_audio module)
Date: Tue, 21 Mar 2017 13:24:30 +0530	[thread overview]
Message-ID: <1490082870.1321124.918129488.4F3143F8@webmail.messagingengine.com> (raw)
In-Reply-To: <s5hk27jjigd.wl-tiwai@suse.de>

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
_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss

  reply	other threads:[~2017-03-21  7:54 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
2017-03-21  5:40     ` Takashi Iwai
2017-03-21  7:54       ` Arun Raghavan [this message]
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=1490082870.1321124.918129488.4F3143F8@webmail.messagingengine.com \
    --to=arun@arunraghavan.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=hdegoede@redhat.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=pulseaudio-discuss@lists.freedesktop.org \
    --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 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.