All of the stack traces thus far appear to be SLUB either detecting or being broken by apparant corruption in the heap. This is almost always caused by use-after-free or double-free of memory allocated from SLUB. In this case as it is always triggered by bluetooth activity it is almost cirtainly a bug in that driver. Some targetted debugging of the memory handling in the driver is required.
** Summary changed: - Kernel Bug in bluetoothd? + [bluetooth] BUG: unable to handle kernel paging request at 000002a80101026c ** Summary changed: - [bluetooth] BUG: unable to handle kernel paging request at 000002a80101026c + [bluetooth] BUG: unable to handle kernel paging request at 000002a80101026c (RIP: __kmalloc_node_track_caller) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901770 Title: [bluetooth] BUG: unable to handle kernel paging request at 000002a80101026c (RIP: __kmalloc_node_track_caller) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/901770/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
