kernel-packages team mailing list archive

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

KarlRelton, as per
http://www.dell.com/support/troubleshooting/us/en/19/Product/latitude-d630
an update is available for your BIOS (A19). If you update to this, does
it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

** Tags added: bios-outdated-a19 needs-upstream-testing regression-
potential

** Attachment removed: "lspci log"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1117608/+attachment/3517643/+files/lspci.log

** Summary changed:

- bluetooth incorrectly removes input devices
+ 413c:8140 [Dell Latitude D630] Bluetooth incorrectly removes input devices

** 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/1117608

Title:
  413c:8140 [Dell Latitude D630] Bluetooth incorrectly removes input
  devices

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Linux kernels after 3.2 introduced battery status reporting for
  devices such as bluetooth keyboards and mouse.

  Unfortunately there is an issue when such input devices are removed:

  - a battery status report is requested
  - this fails, because the device is being removed (communications with it are now down)
  - the failure results in a 5 second wait (the code has a 5 second timeout)

  - the bluetooth hci code has a race condition: the 5 second delay means one thread definitely loses the race
  - the race condition leads to devices in the sysfs tree being removed in the wrong order
  - this leads to udev events being sent out with 'truncated paths'
  - this leads to userspace programs like Xorg evdev ignoring the event, but then getting confused about what keyboard/mice are actually attached
  - this results in bluetooth keyboard/mice not working after a suspend/resume (because on resume the input devices are first removed, and then re-added)
  --- 
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  karl       2108 F.... pulseaudio
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=a82d4a59-432d-4d4b-9d27-557f669eb637
  MachineType: Dell Inc. Latitude D630
  MarkForUpload: True
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_GB.UTF-8
   SHELL=/usr/bin/tcsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-4-generic root=UUID=84c73eda-43e4-429c-8428-0a37de7b6de5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-4-generic N/A
   linux-backports-modules-3.8.0-4-generic  N/A
   linux-firmware                           1.95
  Tags:  quantal running-unity
  Uname: Linux 3.8.0-4-generic i686
  UpgradeStatus: Upgraded to quantal on 2012-10-23 (107 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy lpadmin netdev plugdev powerdev scanner tape video
  WpaSupplicantLog:
   
  dmi.bios.date: 06/20/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvrA12:bd06/20/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1117608/+subscriptions