Brian Rogers wrote:
> The problem still exists on the very latest upstream kernel. I'm going
> to bisect between 2.6.26 and 2.6.27, and report the bad commit to the
> Bluetooth guys. Then it shouldn't be too long before we have a fix.
If you narrow it down to the bad commit, I'll be happy to test it with
my S-E phone, which has similar but not quite the same problems.
(Btw, is it even possible to bisect Ubuntu kernels? A recent article
from lwn.net notes that distro kernels have distro-specific initramfs
setups making it impossible to use vanilla kernels on some laptop
configurations now...)
Brian Rogers wrote:
> The problem still exists on the very latest upstream kernel. I'm going
> to bisect between 2.6.26 and 2.6.27, and report the bad commit to the
> Bluetooth guys. Then it shouldn't be too long before we have a fix.
If you narrow it down to the bad commit, I'll be happy to test it with
my S-E phone, which has similar but not quite the same problems.
(Btw, is it even possible to bisect Ubuntu kernels? A recent article
from lwn.net notes that distro kernels have distro-specific initramfs
setups making it impossible to use vanilla kernels on some laptop
configurations now...)
-- Jamie