[Bug 1165433] Re: Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect
I as well am somewhat disappointed in the handling of this bug, but only for completeness, here I will report that a fix has been found but has not reached a stable release yet. Gianluca has suggested two patches in the linux-bluetooth late last year patched against 3.12.6, and with these two patches I have found that behavior has been restored back to what it was like pre 3.8. This is very preliminary as there still may be latent issues but my inititial testing has indicated that the two patches have finally completely fixed the problem. -- 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: Kernels from 3.8.x to 3.11.x panic 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
[Bug 1165433] Re: Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect
Anyone running into this bug on Ubuntu, please test Linux kernel 3.12-release or newer, if you can compile it (or if there is a package available...) This kernel should have the BT DUN fixes. I really cannot say anything in these forums as I am not running Ubuntu (I have the same bug posted on Gentoo's bugtracker, https://bugs.gentoo.org/show_bug.cgi?id=474432 ) but there are not enough Gentoo users using BT DUN/NetworkManager for me to collaborate with... My observations is that with the 3.12 vanilla kernel the crash goes away if I manually set up an rfcomm link and detach it, but NetworkManager no longer finds BT DUN as a valid dialup device. Reverting back to 3.5.7 or 3.6.11 restores operation with the same userspace. ** Bug watch added: Gentoo Bugzilla #474432 https://bugs.gentoo.org/show_bug.cgi?id=474432 -- 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: Kernels from 3.8.x to 3.11.x panic 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
[Bug 1256811] Re: [Lenovo ThinkPad T400] linux kernel panic on bluetooth DUN disconnect
This will be good to test a new upstream kernel. I know that Kernel 3.12-release contains the proposed fix to BT DUN, however its interaction with blueman/networkmanager is broken. Anyone who has this bug on Ubuntu (or RH/Fedora), please report back, I am interested to hear any success with it. On my Gentoo system I can no longer reproduce the crash on my box but BT DUN no longer works properly with NetworkManager. I may have configured my kernel incorrectly - that's what I want to rule out... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1256811 Title: [Lenovo ThinkPad T400] linux kernel panic on bluetooth DUN disconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1256811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1165433] Re: Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect
More information: Thanks to busybox being installed, I used its microcom utility and tested that the bluetooth RFCOMM link does work as I can submit the AT commands to the modem and the modem responded as expected. I can subsequently shut down the link too with blueman without seeing a hang/crash. In my opinion it seems to be working but there may be a separate unexpected BAPI change going on here. I also want to make a correction here: the more exact error that I got was: Connection Failed: Modem Manager did not support the connection. -- 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: Kernels from 3.8.x to 3.11.x panic 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
[Bug 1165433] Re: Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect
Preliminary: I just tried with 3.12-rc1 with blueman. It doesn't work - if someone else could also try this it would be interesting. When I tried connecting to dialup networking, it claims it "cannot connect to networkmanager" after trying to setup the DUN connection for a few moments - implying there was a dbus issue. However the same setup, when I reboot back to 3.6.11, works fine - so userspace should be working. It may be a kernel config error, but if someone else could also try it would be good. I did see /dev/rfcomm0 get set up, need to try to see if I can do AT commands to /dev/rfcomm0 at least, but I don't have a terminal program installed on this laptop... -- 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: Kernels from 3.8.x to 3.11.x panic 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
I read it as destroying the tty structure before it was completely cleaned up, so future references to the tty struct were pointing to freed memory. Even better it looks like a new version of the patch set was released today Jul 26, in fact just now pretty much, subject "rfcomm: Implement rfcomm as a proper tty_port" where Gianluca writes: "This patchset addresses an issue with the rfcomm tty driver in the current stable kernels that manifests itself as a sudden lockup of the whole machine or as a OOPS if we are lucky enough (I wasn't). Triggering the problem is very easy: 1) establish a bluetooth connection with a bluetooth host 2) open the tty it provides with some program 3) turn off the bluetooth host or take it out of range" which sounds very much like the problem we're seeing. -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
Oh I'm terribly sorry, I am incorrectly referring to LKML when I should have been writing Linux-Bluetooth mailing list. This has not made it to anything yet. -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
Please look at Gianluca Anzolin's patches that were submitted Jul 12 and reviewed by Peter Hurley. I have yet to test this but this looks promising. -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
Looking through LKML, Gianluca has some additional patches on Jul 22. Looks like this is not done yet. I'll say it again, not sure where I said it in the past, this is one big ball of spaghetti that needs to be unwound and not broken further... -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
I just saw a mail fly by on linux-bluetooth and linux-serial mailing lists that seems to be a patch one person made that alleviates the issue. I'm not sure of all the archive areas for the mailing list but as I get from the mail list, look for this message with patch attachment: Date: Sat, 6 Jul 2013 10:43:43 +0200 From: Gianluca Anzolin To: linux-blueto...@vger.kernel.org Cc: linux-ser...@vger.kernel.org, hol...@ahsoftware.de, pe...@hurleysoftware.com Subject: [RFC] PATCH: rfcomm tty refcount fixes -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
This workaround, though the original submitter doesn't think it does
much, seems to at least prevent my machine from crashing...
diff --git a/drivers/tty/tty_port.c b/drivers/tty/tty_port.c
index 6d9e0b2..a4f4fa9 100644
--- a/drivers/tty/tty_port.c
+++ b/drivers/tty/tty_port.c
@@ -140,6 +140,10 @@ EXPORT_SYMBOL(tty_port_destroy);
static void tty_port_destructor(struct kref *kref)
{
struct tty_port *port = container_of(kref, struct tty_port, kref);
+
+ /* check if last port ref was dropped before tty release */
+ if (WARN_ON(port->itty))
+ return;
if (port->xmit_buf)
free_page((unsigned long)port->xmit_buf);
tty_port_destroy(port);
So far the machine still oopses but no hang at least, bluetooth is
completely hosed but it was already hosed anyway...
--
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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
whoops credit to LKML Peter Hurley, forgot to give credit to the writer... (though it's not a fix) -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
I wonder if this is the bug we're running into here... http://marc.info/?l=linux-bluetooth&m=136868678418771&w=2 Will have to study this when I get some time... -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
And once again I need to clarify, this is with Gentoo Linux. When I mention "stop bluetoothd" it's a lot more than just killing it - I meant /etc/init.d/bluetooth stop from the command line. This time I got the oops sync'ed and stored in my syslog. ** Attachment added: "Oops when stopping bluetooth while rfcomm is up" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433/+attachment/3706528/+files/fujikolog.txt -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
Here's another way to trigger the crash: 1. Set up and use rfcomm/btusb as normal. 2. stop bluetooth daemon It's not necessary to disconnect from networkmanager to trigger this. This time the first anomaly is a warning in get_work_pool. This time it says pppd, and it was trying to release the connection. I need to set up serial console again but the call trace is (typed by hand): warn_slowpath_common warn_slowpath_null flush_work ? kfree __cancel_work_timer cancel_work_sync tty_ldisc_halt tty_ldisc_release tty_release __fput fput task_work_run do_notify_resume int_signal Less than one second after, I get a full oops - this time in X, and the call trace is pretty much the same as the previously posted oops. -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
This is Gentoo built, Linux-3.9.2 (from kernel.org): This doesn't seem very helpful for me, all it's pointing to is some massive kernel table corruption. Note that using serial console, the machine still was able to respond to the console but no other i/o was accessable. Every new I/O attempt would generate another oops - the machine is unusable but data can be collected. ** Attachment added: "oops generated from disabling bluetooth DUN in blueman" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433/+attachment/3705113/+files/bluetoothcrash.txt -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
I just reproduced this on my core-i7 x86-64 with the targus USB stick since it has a serial port to do console. Unfortunately the oops dump is not helpful - it says it oops in metacity. Perhaps this is why it's so difficult to debug... Added it anyway, this is the first oops that came from my system. -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
Architecture agnostic for me, it crashes on 3.8.13-gentoo on x86 (32-bit, eeepc 900a, targus USB stick) -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
Ok, confirmed, behavior is different in 3.10-rc5 but still not expected result. It crashed, but this time my machine completely hangs within X11 instead of dropping back to KMS console. Complete hang as before. -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
Before concluding that it is fixed, I subsequently had my 3.10-rc5 hang hours later. Unsure if it was latent damage caused by the same issue as before or another bug... more testing needed. -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
I just tested the raw linux-3.10-rc5 from kernel.org and it appears to not have this issue. -- 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
[Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
I saw this same issue in Gentoo Linux, and also suspecting kernel. I haven't gotten a chance to try newer kernels but 3.8.13-gentoo exhibits this issue 100% of the time. Since I had to apply a patch (probably same as used for other distros whose NM works with BT out of the box) for Gentoo's Networkmanager to see the bluetooth rfcomm, I figure that this would be tough to get support from Gentoo side (I wonder why this patch hasn't made its way upstream?) -- 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
[Bug 583728] Re: NetworkManager ignores the rfcomm port when it gets registered in blueman
Confirmed that this works in Gentoo. I detailed the patch I made on Gentoo Forums (because as-is, the instructions are gentoo specific; but the hack is for networkmanager.) http://forums.gentoo.org/viewtopic-t-926860-start-0-postdays-0 -postorder-asc-highlight-.html Basically I decide to remove the check alltogether, I'm not sure why it's specifically singling out bluetooth, it didn't seem right to simply invert the sense of the check. modem_added calls with const char *driver and if it's "bluetooth" it will always fail. If the sense is inverted, then anything except bluetooth will fail... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/583728 Title: NetworkManager ignores the rfcomm port when it gets registered in blueman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/583728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
