Hi Marcel, On Thu, Oct 31, 2013 at 10:20 AM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > Hi Tim, > >>> As Anderson Lizardo already mentioned, maybe first verify that the x86 >>> kernel 3.4 doesn't have the same problem and that it's really a problem >>> of the ARM kernel. Up to now he didn't say what kernel version he uses >>> on x86. >> >> here's my desktop version: >> $ uname -a >> Linux tzing 3.8.0-32-generic #47-Ubuntu SMP Tue Oct 1 22:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux >> >> I'm trying to get an older version of the kernel running on another machine and then I'll report back > > I actually need to know if bluetooth-next tree still has this issue. That is first and foremost the one thing that needs to be checked. I asked Tim to mention the kernel version on x86 vs. the version on ARM, because I vaguely remember this same issue being reported last year (or even 2011) and being fixed (If I find the patch, I will let you know). As Tim mentions later on, on x86 the issue does not happen on 3.8, but it is present on 3.2 (and I suspect it will also be present on 3.4 on x86 as well). Best Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil -- 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
