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.
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.