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 patc
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 -
implyin
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
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.
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 Ge
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
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 Netwo
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 disconn
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 Ubun
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
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
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 sy
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
wo
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
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/11654
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/b
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
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
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 c
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 blueto
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.n
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
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 d
23 matches
Mail list logo
