[pulseaudio-discuss] [PATCH] bluez: Don't autodetect MTU by default
franchesko.salias.hudro.pedros at gmail.com
Wed Sep 13 08:26:20 UTC 2017
В Ср, 13/09/2017 в 07:33 +0200, Georg Chini пишет:
> On 13.09.2017 07:01, Arun Raghavan wrote:
> > On Wed, 13 Sep 2017, at 09:56 AM, Georg Chini wrote:
> > > On 13.09.2017 05:54, Arun Raghavan wrote:
> > > > This breaks a lot of headsets, so disabling by default. Can be
> > > > re-enabled in configuration for specific hardware where it is
> > > > deemed
> > > > necessary.
> > > >
> > > > Also added some debug logging to be able to examine what MTU
> > > > size is
> > > > reported by the device.
> > > >
> > > > BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=102660
> > > > ---
> > >
> > > I think the patch should also address the crash that occurs when
> > > the MTU reported by the kernel is odd. I am not sure what to do
> > > in that case: Round down to an even value (which does not seem
> > > to produce sound) or fall back to 48.
> > I missed that -- can you link me to the mail/big that you are
> > referring
> > to?
> > -- Arun
> The kernel reports an MTU of 183, that makes PA crash with
> sink.c:1380 "pa_assert(pa_frame_aligned(length, &s->sample_spec));"
> pulseaudio-discuss mailing list
> pulseaudio-discuss at lists.freedesktop.org
Yes. Week of crashes. Archlinux start use pulse v11.
My headset work fine only with 48 mtu.
More information about the pulseaudio-discuss