(In reply to Takashi Iwai from comment #2) > Likely relevant: > https://patchwork.kernel.org/patch/9528415/ Yes, you are correct. This could fixed this issue, but after 2017/2/14 the author sent to upstream, there are no more information and those patches didn't merge in to bluetooth or bluetooth-next.