kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

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
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

-- 
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