** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Summary changed:
- Kernel 3.8.x panics on bluetooth DUN disconnect
+ Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Gianluca Azolin's patches were merged to net-next day before yesterday.
And yesterday they were merged to Linus' master branch. So patches will
be in 3.12 rc1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, forgot the links to the commits:
https://git.kernel.org/cgit/linux/kernel/git/davem/net-
next.git/commit/?id=e7abfe40928f4f8c1aa908477c36c13843bd1a57
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cc998ff8811530be521f6b316f37ab7676a07938
--
You received this
Gianluca Anzolin writes on bluetooth-linux mailing list that though his
tty refcount patch series is needed, more work is required to fix the
problem. If I understood his mailing list message correctly, the system
locks up when the device is released even after his patches have been
applied.
The patch series is apparently too extensive to consider for -stable
[1]. So another solution is required for stable kernels. Gianluca's fix
should eventually end up in mainline though (3.12 hopefully).
[1] http://marc.info/?l=linux-bluetoothm=137762583515880w=2
--
You received this bug
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
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189998 and this
bug duplicate each other.
--
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
Actually, there are at least three bug reports on this same problem on
launchpad:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189998
--
You received this bug
Gianluca Anzolin's patches that should fix this problem have now been
merged to bluetooth-next. Eventually they should find their way to
mainline and stable kernels.
http://marc.info/?l=linux-bluetoothm=137699050920055w=2
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-
Apparently the patches do not include the cc tag for
sta...@vger.kernel.org in the sign-off area which assures that when
applied to the stable tree they are applied also to the stable kernels
without anything else needing to be done by the author or subsystem
maintainer.
Should Gianluca Anzolin
*** This bug is a duplicate of bug 1144322 ***
https://bugs.launchpad.net/bugs/1144322
** This bug has been marked a duplicate of bug 1144322
[Toshiba Satellite A80] Kernel 3.8.x Panic when disconnecting from network
manager via ppp0
--
You received this bug notification because you are
Sergio Callegari, could you please test the latest upstream kernel available
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional upstream developers to examine the issue. Please do not test the
daily folder, but the one all the way at the bottom. Once you've tested
I am having similar kernel panics while using a USB bluetooth dongle to
connect my new desktop (Ubuntu 13.04, kernel 3.8.0-27-generic) to a
bluetooth external speaker via A2DP. I went through the correspondence
between Gianluca Anzolin et. al. in linux-bluetooth email list, and it
seems like the
ekin, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control
team, and Ubuntu Bug Squad would like you to please file a new report by
executing the following in a terminal:
ubuntu-bug linux
For more on this, please see the official Ubuntu documentation:
Ubuntu Kernel Team:
deadprogram, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug
Control team, and Ubuntu Bug Squad would like you to please file a new report
by executing the following in a terminal:
ubuntu-bug linux
For more on this, please see the Ubuntu Kernel team article:
Actually, there should be no need to ask for the ubuntu-bug report to
users that are merely confirming a bug for which everything is already
known and everyone is merely waiting for Gianluca Anzolin's patches to
land on the stable update kernel channels.
BTW, ubuntu-bug is quite buggy itself. I
This is definetly still problem, it impacts running 13.04 on a brand new
Dell XPS 13 Developer Notebook.
--
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
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-bug-exists-upstream-v3.9-rc7
--
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
Sergio Callegari, thank you for taking the time to report this bug and helping
to make Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal on just one of the
computers this is reproducible on:
apport-collect 1165433
When
Ubuntu bug is buggy and hangs all the time with You are already logged
in You are already logged in as Sergio Callegari. If this is not you,
please log out now. To make it work, you need to log-out and rerun
apport-collect, not nice. Plus, I am now trying 3.10.3 and obviously
apport is unhappy
Thanks for the notice about the Linux-BT ML... I was looking at the
latest posts by Gianluca Anzolin on LKML and that is why I was confused.
This ones look really quite promising.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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.
Isn't this just fixing a leak? Namely, that an object is not destroyed when it
should so memory is wasted?
From previous messages on LKML the issue causing the crash seemed to be the
opposite... that an object is destroyed and then its data is used again
causing memory corruption...
--
You
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.
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
Ante Bucan (abucan) wrote:
If you logout and login again, the name of the connection is correct again
and you can connect without a problem.
Instead of logout and login I uncheck at use DUN connection for my mobile and
create connection again to prevent closing other programs.
--
You
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
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
Unfortunately, since 3.9.8 it is not anymore possible to test mainline kernels
on raring.
Won't be easy to say if things get fixed or not upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I wonder if this is the bug we're running into here...
http://marc.info/?l=linux-bluetoothm=136868678418771w=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.
Looks very likely. But also bad, since rfcomm is among the top users of
this and linux BT people knew there was something wrong since
http://marc.info/?l=linux-bluetoothm=136386669411447w=2, with more
info in http://marc.info/?l=linux-bluetoothm=136537407411019w=2, or
maybe even earlier, e.g.
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
Can someone please make this quick test?
1) Get out of X (e.g. by logging out the graphical desktop and switching to a
virtual terminal)
2) Use nmcli to connect and disconnect from the BT dun connection
Do you still /always/ see the kernel oops?
--
You received this bug notification because
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
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
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
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
For me, even with 3.9 this is the case. When I try to disconnect from
DUN, at times I get thown to the text console with an oops. At times I
just see the machine freeze in X11. At times the machine keeps working
in X11 for a few seconds (or up to 1 minute), and in this case I can
even see the oops
Incidentally, it is still there in brand new 3.9.6.
And I had exactly the behavior indicated above.
After disconnection the machine keept running fine for about 1min to
completely freeze right after.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
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,
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
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
Reproducible on linux-image-3.8.0-21-generic. Not yet reproducible on
linux-image-3.10.0-031000rc3. Would bissect help?
--
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
3.9.2 still affected.
Why is this bug still marked incomplete rather than confirmed? Marking
as confirmed after reports #11 and #10.
Thanks to Ante for the workaround.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a
I also have this problem on Xubuntu 13.04. When I disconnect the
connection, there is a kernel panic. If you try to restart the machine
without disconnecting, there is also a kernel panic.
There is a workaround. You click on the bluetooth icon and disable the
bluetooth. The connection drops
I have just upgraded from 12.10 to 13.04 andi have the same issue,
kernel panic when disconnecting from DUN bluetooth, on an Asus eeepc
1005ha.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1165433
Same issue with my Nokia C7 (stock 13.04 x86). One thing that I noticed
is that the NetworkManager indicator is having trouble displaying the
name of the connection, it looks approximately like this:
---
Nokia C7-00 N
No description
Disconnect
---
Sometimes instead of No description, it shows
Bug is also in the just released upstream 3.8.9... and, as shown by the
previous report, in Ubuntu Raring...
Together with bug 1112652 it looks like 3.8.x is a bit of a network killer...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yes, the bug is also in the latest kernel. Sorry for the mispell in #4.
That was 3.9 RC6!
--
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
Not fixed in 3.9RC7 either.
** Tags removed: regression-release
** Tags added: kernel-bug-exists-upstreamse regression-relea
** Tags removed: kernel-bug-exists-upstreamse regression-relea
** Tags added: kernel-bug-exists-upstream regression-release
--
You received this bug notification because
The bug is also present in 3.6.9RC6
--
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:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.9 kernel[0]. You will need to install both the linux-image and linux-
image-extra .deb packages.
If this bug is fixed in the mainline kernel, please
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
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
Cannot attach the apport collect data, since I am not on the machine
where I first saw the issue.
However, not only I can confirm the bug, but also report that I am now
sure it is not restricted to the DELL E6500 host on which I first saw
it.
It is 100% reproducible also on a desktop machine
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
59 matches
Mail list logo
