To Jussi...
as the original reporter of this bug, I think it has no hope of being fixed
even if you provide all the relevant kernel commits.
Which is bad, because the crash is serious and happens 'late' when may kernel
data structures may have been written over, with potential data loss.
I
I managed to find one more bug report similar to this one. So now there
are at least four bug reports (including this one) here in Launchpad on
this problem:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433
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
There is no activity from me because I have unsubscribed from the bug...
it is just by chance that I am reading this now.
This bug has been investigated and fixed in recent linux ages ago and
Jussi, eccerr0r and I have provided all the relevant information and
pointers in this thread. It has also
eccerr0r, please do not solicit others to post comments here as Me too!
comments wouldn't be helpful at this point. If you are using Gentoo, it would
be best to engage the Gentoo developers for assistance. Despite this, so your
hardware may be tracked, using Ubuntu, could you please file a new
Sergio Callegari, this bug was reported a while ago and there hasn't
been any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
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
I opened a new bug report for the issue: #1256811
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1165433
Title:
Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect
Status in
Confirmed since I can reproduce this on precise x64.
See bug #1256811
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags removed: needs-apport-collect needs-bisect needs-crash-log
** Tags added: kernel-bug-exists-upstream-v3.8 precise
** Tags removed:
nitto, 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 while booted into a Ubuntu repository
kernel (not a mainline one) in a pre-3.8.x release via:
ubuntu-bug
My system is affected by the bug too.
Beacuse of the freeze I cannot post a bug-report, I can only attach this
picture.
If I can dump something useful or post any other information please tell me how.
Regards
Nitto
** Attachment added: DSCF5101.JPG
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
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
Hey developers/bugzappers, same bug in vanilla kernel 3.10.12 on CentOS
6.4, is a kernel bug. I reported today to kernel.org
track and help me please.
https://bugzilla.kernel.org/show_bug.cgi?id=61431
** Bug watch added: Linux Kernel Bug Tracker #61431
Nix, it would be best to report this to your distro -
http://bugs.centos.org/main_page.php
If you can reproduce this in Ubuntu, please file a new report via a terminal:
ubuntu-bug linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Fixed the bug title (so that the window of affected kernels is clear and
it is clear that this is an issue both for raring and for saucy.
Also marked as confirmed, since the incomplete label was a bit weird at
this point.
If I understand correctly the situation now is this
1) All kernels from
Sergio Callegari, please execute the following command with a computer you can
reproduce the issue with, as it will automatically gather debugging
information, in a terminal:
apport-collect 1165433
When reporting bugs in the future please use apport by using 'ubuntu-bug' and
the name of the
For the 10th time, tried. Hangs. Apport-collect is buggy and needs
inconvenient workarounds to be used. Please push to have it fixed,
otherwise it won't be used. If it worked fine, it would have been used
it since the first time.
In any case I cannot see how a bug for which there are kernel
** Tags removed: kernel-bug-exists-upstream-v3.9-rc7 needs-apport-collect
needs-bisect needs-crash-log needs-upstream-testing regression-potential
** Tags added: kernel-bug-exists-upstream-v3.11.0
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags removed: kernel-bug-exists-upstream-v3.11.0
** Tags added: kernel-bug-exists-upstream-v3.11 needs-apport-collect
needs-bisect needs-crash-log needs-upstream-testing regression-potential
** Tags removed: needs-upstream-testing
--
You received this bug notification because you are a
20 matches
Mail list logo
