Comment 51 for bug 1165433
Revision history for this message
| Sergio Callegari (callegar) wrote Re: Kernel 3.8.x panics on bluetooth DUN disconnect | #51 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
If the patch series is not applied, after 6 months of raring there will be 6 more months of saucy without the possibility to use the bluetooth tethering facility (bluetooth DUN) offered by mobile phones. Sounds bad.
In any case if this patch set is too extensive to apply, the obvious conclusion is that the not-too-extensive patch to apply is disabling rfcomm altogether in 3.8, 3.9, 3.10, 3.11. As is, rfcomm is totally broken, unusable and quite dangerous. It makes the kernel crash systematically at every use. Furthermore, the crash is due to kernel data being randomly rewritten with garbage, which means that the actual crash may happen *seconds to minutes after the actual issue provoking it* (seen > 40 sec personally). It is a bad situation that can easily lead to severe data loss in addition to down time.