On 1 February 2018 at 20:01, Julia Cartwright <julia@xxxxxx> wrote: > On Thu, Feb 01, 2018 at 10:58:28AM +0100, Mirza Krak wrote: >> Hi. > > Hello Mirza. > > [..] >> I have tried running a 4.14.15 vanilla kernel, and this does not have >> this problem which means that it is the following combo >> >> RT + USB Bluetooth >> >> That seem to the problem. >> >> Before I start digging deep in to the stacks I wanted to post my >> problem to the community to see if someone is having a similar problem >> on a different hardware or if you have any pointers on how to further >> debug this. > > One suggestion I would have would be to re-do your testing on mainline > v4.14.15 booted with the 'threadirqs' kernel command line parameter. > > The reason being that without this option, interrupts aren't threaded in > mainline, so it very well could be that your hardware is still > misbehaving, however it's execution time just isn't being accounted for > in the same way. Thank you for the hint. Adding "threadirq" on the mainline kernel exposed the CPU load and I guess that this is not a RT problem then. Thank you once again. -- Med Vänliga Hälsningar / Best Regards Mirza Krak -- 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
