Does the same problem still occur in 2.6.26-rc7? Does it occur if you
rmmod ehci-hcd?
Machine lockups are awfully hard to debug. Can you get any information
at all (like Alt-SysRq-T) when this happens? Can you add debugging
printk statements to the USB bluetooth driver to try and localize where
the hang occurs?
Knowing this doesn't help much without more information.
Do you have any idea why nobody else has reported this sort of problem?
Is it reproducible on other machines?
Alan Stern
--