Hi, On Thu, Feb 8, 2018 at 5:15 PM, Julien Nicoulaud <julien.nicoulaud@xxxxxxxxx> wrote: > 2018-02-07 7:52 GMT+01:00 Vincent Petry <pvince81@xxxxxxxxxxxxxx>: >> >> Hi Luiz, >> >> Can you give me some pointers where I should put the gdb breakpoint to >> get a useful trace ? >> >> I also saw that there is some DBG function logging things. How do I >> enable this logging and from where can I get its output ? Useful would >> probably to log some internal state with and without returning from suspend. >> >> Regarding the breaking patch, it seems to be related to some advertising >> API that used to be marked experimental and is now not experimental any >> more in 5.48. >> Does maybe pulseaudio use this API and had a fallback at the time said >> API was disabled ? And now that it's enabled its code path changed and >> maybe triggered a hidden bug ? Would need to look at the pulseaudio >> bluetooth source code. >> Or does the patch in question enabled advertising where no advertising >> was done before ? Maybe it is advertising too early at a time where the >> system hasn't fully resumed from suspend ? >> >> My pulseaudio version: pulseaudio-11.1-2.1.x86_64 >> >> Would be good if the other affected users post their distro + pulseaudio >> versions for cross-reference. > > Hi, I am also affected by this since updating to bluez 5.48. > > My distro is Arch Linux, pulseaudio 11.1-1, linux 4.14.15, using a > Bose QuietComfort 35 headset with an Asus zenbook laptop (Intel 7260 > wireless chip). > > Please let me know if I can be of any help. Please check with the patch Ive sent yesterday: core: Fixes order InterfaceAdded -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
