kernel-packages team mailing list archive

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

Seva Gluschenko, 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 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 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.11-rc5

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

** Package changed: udev-extras (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
       Status: New => 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/513777

Title:
  Karmic (9.10): bluetooth initialized but unavailable, Toshiba
  Satellite U400-24K

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: udev-extras

  /var/log/kern.log:
  Jan 28 15:55:00 gvs kernel: [    0.000000] Linux version 2.6.31-18-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #55-Ubuntu SMP Fri Jan 8 14:55:26 UTC 2010 (Ubuntu 2.6.31-18.55-generic)
  ...
  Jan 28 15:55:00 gvs kernel: [    0.000000] DMI present.
  ...
  Jan 28 15:55:00 gvs kernel: [    0.000000] ACPI: BIOS bug: multiple APIC/MADT found, using 0
  Jan 28 15:55:00 gvs kernel: [    0.000000] ACPI: If "acpi_apic_instance=2" works better, notify linux-acpi@xxxxxxxxxxxxxxx
  ...
  Jan 28 15:55:00 gvs kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-18-generic root=UUID=63e1b95c-d691-43c1-b4ad-00e764e73296 ro quiet splash
  ...
  Jan 28 15:55:00 gvs kernel: [    1.359147] PCI: Using ACPI for IRQ routing
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.0: BAR 13: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.0: BAR 14: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.0: BAR 15: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.4: BAR 13: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.4: BAR 14: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.4: BAR 15: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.5: BAR 13: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.5: BAR 14: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.5: BAR 15: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.368009] Bluetooth: Core ver 2.15
  Jan 28 15:55:00 gvs kernel: [    1.368021] NET: Registered protocol family 31
  Jan 28 15:55:00 gvs kernel: [    1.368021] Bluetooth: HCI device and connection manager initialized
  Jan 28 15:55:00 gvs kernel: [    1.368021] Bluetooth: HCI socket layer initialized
  Jan 28 15:55:00 gvs kernel: [    1.368021] NetLabel: Initializing
  ...
  Jan 28 15:55:00 gvs kernel: [    2.279773] NET: Registered protocol family 17
  Jan 28 15:55:00 gvs kernel: [    2.279788] Bluetooth: L2CAP ver 2.13
  Jan 28 15:55:00 gvs kernel: [    2.279790] Bluetooth: L2CAP socket layer initialized
  Jan 28 15:55:00 gvs kernel: [    2.279793] Bluetooth: SCO (Voice Link) ver 0.6
  Jan 28 15:55:00 gvs kernel: [    2.279794] Bluetooth: SCO socket layer initialized
  Jan 28 15:55:00 gvs kernel: [    2.279830] Bluetooth: RFCOMM TTY layer initialized
  Jan 28 15:55:00 gvs kernel: [    2.279833] Bluetooth: RFCOMM socket layer initialized
  Jan 28 15:55:00 gvs kernel: [    2.279835] Bluetooth: RFCOMM ver 1.11
  Jan 28 15:55:00 gvs kernel: [    2.280461] Using IPI No-Shortcut mode
  ...
  and that's it. Neither bluez-utils, nor hcitool can find bluetooth devices. Turning killswitch off/on resets WLAN and Bluetooth, but the latter remains unavailable. Tried omnibook module from trunk, unsuccessfully (didn't recognized chipset). Tried 2.6.32-6 kernel with the same effect. Didn't succeed with hid2hci 'cause didn't find proper options.

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