Tested 3.10.2 from the mainline ppa (in spite of the bad experience with
3.9.8 that is broken).
The linux bluetooth screen of death is still there, 127 days since first
notification on the LKML for a fully reproducible regression that
completely impairs a subsystem and causes a hard kernel crash with a
disastrous memory corruption, sigh.
Specifically, the RFCOMM session disconnection fixes that got applied to
Linux 3.10 commits (8 off) 24fd642ccb24c8b5732d7d7b5e98277507860b2a to
fea7b02fbf73adb2e746f00ed279a782de7e74e4 do not help.
All LKML activity on this stopped on 2013-06-25. From it it looks like
kernel developers seem to believe that to reproduce the bug a hard power
down of the remote is necessary ('Yes. With power down I meant a hard
power down, such that the remote doesn't has the chance to close the
session cleanly.'). Looks like this is not the case. A simple bluetooth
DUN activation / deactivation cycle from network manager (targeting a
Galaxy S mobile phone that is never switched off) seems to trigger the
bug and the kernel crash here. They may also thik that the bug is fixed
with the latest RFCOMM session disconnection fixes or that at least it
is reduced in scope (so that only a process is killed and a TTY not
released, without the disastrous memory corruption in the kernel).
Either here we are discussing a completely different bug from that in
the LKML thread http://news.gmane.org/find-
root.php?message_id=%3c519480A1.6030909%40ahsoftware.de%3e or the kernel
developers miss some relevant information.
Can someone from the ubuntu kernel team forward this info to Alexander
Holler and others on the LKML list revitalizing the thread?
In the meantime, may I again suggest unconfiguring RFCOMM TTY support
from ubuntu production kernels as a SRU until this is fixed, so DUN
still remains unfunctional, but at least the kernel crashes that may
lead to data loss are prevented? The thread on LKML does not exclude
data loss '[crash reports] don't make much sense because they happen
because of a disastreous memory corruption, which means the BUGs can
include almost everything (hopefully nothing which eats your disk
contents).'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1165433
Title:
Kernel 3.8.x panics on bluetooth DUN disconnect
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
