I've cherry-picked e2e407dc093f530b771ee8bf8fe1be41e3cea8b3 on to
4.4.0-28.47 and compiled the kernel and it looks like this did solve the
issue. (Just tested for 15 minutes, but with the default kernel it
appeared within seconds already).
--
You received this bug notification because you are a m
Christopher,
I'm hitting this bug too on my Thinkpad x250 with a dockingstation and two
external displays.
I'm happy to test, but haven't built a kernel in a long time. Any guidance on
how to apply that commit?
Is it like this:
https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_rel
I investigated this bug today and discovered two things.
If i boot with Kernel 3.8.0-35 (latest raring Kernel) I do not encounter this
bug.
For Saucy I found a workaround and some kind of a fix.
Workaround:
I can enable bluetooth from a shell using "sudo rfkill unblock bluetooth"
http://askubuntu
