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 been clarified in LKML that due to the type of bug it is quite meaningless to provide traces and that this bug may cause data loss due to corruption of the kernel data structures. Yet, dangerous as it is, and regardless of the many users confirmig the issue, the bug remains unconfirmed because there is no apport-collect that is considered much more important than all the other info. And since the bug is not confirmed, the ubuntu kernel developers are just ignoring the report and all the useful pointers to upstream discussion. And not surprisingly ubuntu remains unfixed months after the upstream fix. Similarly not surprisingly duplicate bug reports spring out without being recognized as such. Unfortunately, I must say that I really find it a waste of time to report bugs and spend time in checking the LKML and provide pointers to the root relevant discussion there and pointers to upstream patches that fix the issue in this condition. And this is why I gave in. Also it is a bit sad that eccerr0r is invited not stay out of the discussion in the duplicate 1256811 just because his main OS is gentoo. I am also really sorry to say that the management of this bug report seems to me as all rules and bureaucracy and zero substance, but I hope that this can be accepted as constructive criticism, since I'm also taking the time to try to explain why I'm getting this impression. -- 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 “linux” package in Ubuntu: Incomplete Bug description: Issue is obviously in the kernel that should not panic in any circumnstances. This bug is seen on quantal using the kernel from PPA mainline. Tested with 3.8.0 to 3.8.6. Since 3.8.x is going to be the raring kernel I believe that this should definitely be fixed before raring is shipped. Seen on: DELL E6500 with kubuntu quantal 12.10 64 bit and as said, kernel 3.8.6 from the mainline ppa. The machine has a Dell Computer Corp. Wireless 370 Bluetooth Mini-card (connected via an internal usb connection). The issue is shown when connecting to the internet via a Samsung Galaxy S plus phone, using a bluetooth DUN connection. It is reproducible every time. How to reproduce: 1) Use the bluetooth applet to discover the phone and associate to it. 2) Use network manager to setup a DUN connection with the phone through your APN 3) Connect to the internet via bluetooth DUN (connection works perfectly) 4) Disconnect from the network manager. At the same time you disconnect, the GUI session is terminated and the kernel panics, briefly showing a panic log on the screen. Note that: a) The issue is not present using the standard ubuntu quantal kernel b) The issue is not present using kernels from the mainline ppa before 3.8 (e.g., 3.7.x is fine for all x) c) The issue is not present when connecting to the internet using a USB mobile dongle (e.g. Huawei usb key) This looks pretty serious to me: kernel does not sync when panicing and there is a serious risk of data loss; connecting to the internet via a smart phone using bluetooth DUN seems to be something that one should take for granted on any modern OS. Furthermore, points a) and b) above show that this is a *regression* over previous kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
