no bluetooth after kernel update to 2.6.27-7-generic

Bug #281949 reported by techno-mole
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Stiff

Bug Description

hello again.

well the good news is that since the kernel went from 2.6.27-6-generic to 2.6.27-7-generic my nvidia driver issue seems to have been fixed, but for some reason my bluetooth adapter no longer works.

its like it was before on hardy, basically i use a usb bluetooth adpter for connecting to my mobile, it didnt work on hardy, but did on gutsy, it did work on the beta of intrepid, but now it doesnt.

when i put the adpater into any usb port on my system nothing happens, and by that i mean nothing, no application trying to load, but then crashing, just nothing.

the adapter is working perfectly when run on windows.

cheers

(currently running intrepid ibex (kubuntu) 8.10 beta, kernel 2.6.27-7-generic)

Revision history for this message
Alexander Butenko (avb) wrote :

i have the same issue. Mine adapter is dlink dbt-122.
Here is a snip of dmesg:
[138209.665630] Bluetooth: Generic Bluetooth USB driver ver 0.3
[138209.666632] usbcore: registered new interface driver btusb
[138214.844410] hci_cmd_task: hci0 command tx timeout
[138219.848340] hci_cmd_task: hci0 command tx timeout
[138224.853676] hci_cmd_task: hci0 command tx timeout
[138229.856417] hci_cmd_task: hci0 command tx timeout
[138234.860719] hci_cmd_task: hci0 command tx timeout
[138239.960585] hci_cmd_task: hci0 command tx timeout
[138240.464277] bluetoothd[5133]: segfault at 3 ip b7e39938 sp bfb8fcc8 error 4 in libc-2.8.90.so[b7dc8000+158000]

Revision history for this message
Alexander Butenko (avb) wrote :

after doing some researches i found this info: http://kerneltrap.org/mailarchive/linux-netdev/2008/9/8/3233464. Probably a regression appear because of it.

Revision history for this message
VladimirCZ (vlabla) wrote :

I have similar problem.

My USB bluetooth adapter worked well under Hardy.
Under Intrepid (installed beta from scratch and updated) the Bluetooth manger can only detect connectible devices in neighborhood, but any attempt for pairing them is unsuccessful - there appears no dialogues for "key" both on my PC and mobiles. I have tried to connect two Nokia phones 6021 a 6310i. (Note: under WinXP it still works => no hardware failure)

USV bluetooth adapter:
Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

OS Ubuntu 8.10 beta 64-bit (2.6.27-7-generic)
Motherboard Asus P5KPL (Intel chipset with Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GH)

Revision history for this message
tielie (mike-tielie) wrote :

Same here on the same BT chipset

 ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

Revision history for this message
techno-mole (techno-mole) wrote :

im just updating my problem, which i regret to say still is a problem.
there have been quite a few updates of late, but none of them have helped the bluetooth problem i have.

i noticed that there was an update to something bluetooth related in the updates i received today, but still no luck.
the adapter is just a cheap one, but it has a driver disc that installs broadcom drivers when you use the thing with windows, so maybe the problem is that the adapter is no longer compatible with the new kernel ?
although it worked perfectly in gutsy, but stopped working under hardy, and hasnt worked since.

i have tried on both 32 and 64 bit versions of kubuntu, but the result is the same, that being it doesnt work.
i do think that the system knows somethings been plugged into a usb port, it doesnt know what though, and to be honest im not sure what to do to find out if the system does actually see it, is there a command i could enter in a terminal ?

Revision history for this message
Mario Limonciello (superm1) wrote :

To the posters with issues here:
Quirks may be needed for your adapters possibly.

Try the most common one:

sudo rmmod btusb && sudo modprobe btusb reset=1

If this works for you, please post the exact device ID from lsusb and a quirk can get added to the kernel for you.

Changed in bluez:
status: New → Incomplete
Revision history for this message
Alexander Butenko (avb) wrote :

Bus 004 Device 002: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

reset=1 doesn't works for me.

[ 119.100433] hci_cmd_task: hci0 command tx timeout
[ 124.104382] hci_cmd_task: hci0 command tx timeout
[ 129.112651] hci_cmd_task: hci0 command tx timeout
[ 134.116838] hci_cmd_task: hci0 command tx timeout
[ 139.116772] hci_cmd_task: hci0 command tx timeout
[ 144.156229] hci_cmd_task: hci0 command tx timeout
[ 157.408557] hci_cmd_task: hci0 command tx timeout
[ 168.048719] hci_cmd_task: hci0 command tx timeout
[ 179.089032] hci_cmd_task: hci0 command tx timeout

Revision history for this message
techno-mole (techno-mole) wrote :

hello again.

i tried the code provided (sudo rmmod btusb && sudo modprobe btusb reset=1)
 but it didnt do anything im afraid.

at least i now know that my adaptr is being seen by the system, it just doesnt load anything up so i can use it, although i would like to point out that when i switched from ubuntu to kubuntu my bluetooth worked, but when i upgraded to kde 4.1 the bluetooth stopped altogether, this happened on 2 different machines, and i would guess that if i upgraded to kde 4.1 on one of the other systems the same would happen.
i dont know if its relevant, but i thought id mention it.

the out put from lsusb is -

Bus 004 Device 003: ID 0dda:2026 Integrated Circuit Solution, Inc. USB2.0 Card Reader
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 062a:0000 Creative Labs Optical mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 014: ID 0a5c:2100 Broadcom Corp. Bluetooth 2.0+eDR dongle
Bus 001 Device 013: ID 0a5c:4500 Broadcom Corp.
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Revision history for this message
VladimirCZ (vlabla) wrote :

1) In my first message was a small inaccuracy. In fact my USB bluetooth with KY-BT100 chipset worked well in original intrepid beta installation but lost its full functionality after upgrading to newer kernel.

2) I can pair mobile phones to my PC, but only when I start pairing from a phone to be paired. Unfortunately after pairing there is no "mounted phone icon" on a desktop / in nautilus and I cannot browse the mobile from PC even neither through the bluetooth applet "browse" option. Instead a message appears always with some delay - please, find it enclosed.

3) The reset=1 does not work for me.

Revision history for this message
techno-mole (techno-mole) wrote :

well another day and another update, but still no bluetooth, i tried the code again (sudo rmmod btusb && sudo modprobe btusb reset=1) but no joy, the system still sees the dongle, but doesnt seem to be loading anything to actually use it.

i did try pairing from my mobile to see if the phone could sees the pc, but it doesnt, but then i guess if no application is loaded to use the bluetooth then the phone isnt going to see it.

one question though, are some bluetooth adapters working better than others ? eg - do belkin adapters work, while broadcom ones arent ? , that kind of thing, the reason i ask is because i was thinking of getting another adapter to see if that one would work, they arent exactly expensive, ebuyer have some cheap ones.

Revision history for this message
VladimirCZ (vlabla) wrote :

Having installed today's upgrade of HAL I can now pair my mobiles (starting the pairing procedure) from PC. But still after pairing there is no "mounted phone icon" on a desktop / in nautilus and I cannot browse the mobile from PC even neither through the bluetooth applet "browse" option. And the same error message appears like before.

Revision history for this message
techno-mole (techno-mole) wrote :

at least there is some progress for some, after yesterdays hal update, and todays updates (monday 27th of october) i still have no functioning bluetooth, i have tried to pair from the phone, but it doesnt see the pc so still no dice for working bluetooth.

i did try an experiment, i got another bluetooth adapter (belkin) and trying to be clever stuck it in a usb port to see if it would work, but it didnt, and after doing " lsusb " in terminal found it to be another broadcom related bluetooth adapter, so now i have 2 non working usb adapters, but at least i have a spare if one stops working :-)

Revision history for this message
techno-mole (techno-mole) wrote :

i have just been messing around with my bluetooth adapters again, i havent managed to get them working, but when i ran this in terminal - sudo rmmod btusb && sudo modprobe btusb reset=1

i got this message - Module btusb does not exist in /proc/modules

im not sure what i did to get this error, but is it related perhaps to the bluetooth not working ?

Revision history for this message
Sukochev Roman (Leolik) (leolik) wrote :

I have D-Link Corp. [hex] DBT-122 Bluetooth adapter and It's not working in Ubuntu 8.10 Release , how as in Alexander Butenko in first message. Bluetooth adapter worked well under 8.04 Hardy.
When I use "sudo rmmod btusb && sudo modprobe btusb reset=1" device founded, but sending files or other operations with device - not working.

Revision history for this message
techno-mole (techno-mole) wrote :

hello, just updating my original bug report.

i now have bluetooth working under kubuntu intrepid (8.10) i can pair devices and move files between them, and so far i havent run into any problems.

however im not using the kde bluetooth packages, i have been trying to get it to work for a while and had no luck, so i tried compiling myself, and didnt get any where, so i removed all the bluetooth related stuff from my system, then after reading a few items online i found a solution (on launchpad actually - bug report - Bug #280997:) after reading through until about halfway down i found some one had done this -

 Niels Ganser wrote on 2008-10-25: (permalink)

Scott, I just aptitude installed bluez-gnome and ran bluetooth-applet. Worked out of the box for me.

so i tried it and it worked, it may not be ideal but it does work (well it did for me) it might be an idea to remove any bluetooth packages first before trying it, and you will also need the bluetooth file sharing application which can be installed using add/remove programs.

so if any one hasnt already tried this, give it a go and see if it works.

Revision history for this message
Vladimir Ivanov (ivanov-bg) wrote :

After updating my Ubuntu 8.04 LTS to 8.10 Intrepid the Bluetooth stopped working .The Bluetooth manger can only show what devices are connectible in neighborhood, but can't pair them. Only 1-2 time I saw the dialogue for "key" only for few seconds and disappear.
My bluetooth adapter is based on Integrated System Solution Corp chip, too.

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

Another "me too" :
USB Device 1131:1004, I can pair my phone and my computer, but that's all. At least, with 2.6.27-9-generic. I tried with 2.6.24-21-generic (from hardy), and I was able to browse the phone through Bluetooth ...

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

Notice that I have the exact same error, that is "hci_cmd_task: hci0 command tx timeout", on a freshly compiled 2.6.27.7 under debian lenny ...

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

Notice also that this kernel has been compiled from vanilla sources, grabbed a couple of hours ago. So, seems like the problem lies in the mainstream sources.

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

Current 2.6.26-1-686 from Lenny works.

Revision history for this message
Stiff (stiff.ru) wrote :

Problem is same
Bus 002 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
2.6.27-9-generic

with kernel 2.6.24 works fine

Changed in linux:
assignee: nobody → stiff11
status: Incomplete → Confirmed
Revision history for this message
mixon (mbug) wrote :

I think I have the same problem...

---
mixon@mnsv:~$ hcitool scan
Scanning ...
 00:22:65:8E:03:6E
 00:1A:16:34:B8:B4

mixon@mnsv:~$ sdptool browse 00:22:65:8E:03:6E
Failed to connect to SDP server on 00:22:65:8E:03:6E: Connection timed out

mixon@mnsv:~$ lsusb
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

mixon@mnsv:~$ lsmod | grep blue
bluetooth 61924 12 sco,bnep,rfcomm,hidp,l2cap,btusb
---

Is there any solutions for 2.6.27-9-generic yet?

Should I try different kernel?

Revision history for this message
Sami Mäkinen (sami-makinen-helsinki) wrote :

Me too ...

I have the same device and same problem as Alexander Butenko, i.e. 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

I also have a laptop/UMPC with 044e:300d Alps Electric Co., Ltd built-in bluetooth which also is broken in 8.10, but works fine in 8.04

PS: I think importance should be set to High, since this bug completely breaks some pretty important core functionality. Without bluetooth I lose external keyboard (must-have for writing anything longer than a paragraph), mobile internet access (required outside WLAN) and possibility to transfer files from/to mobiles (and other BT devices, where SCP is not available).

Revision history for this message
Sami Mäkinen (sami-makinen-helsinki) wrote :

Actually the Alps Electric bluetooth seems to at least partially work, so perhaps there the problem is in Bluez and not the kernel module. D-Link remains a problem though.

Revision history for this message
Akdo (menoft) wrote :
Download full text (5.6 KiB)

Hi there same problem

Bluetooth device :
[ 615.993748] Bluetooth: Generic Bluetooth USB driver ver 0.3
[ 615.995219] usbcore: registered new interface driver btusb

On research !
[ 621.220435] hci_cmd_task: hci0 command tx timeout
[ 626.225104] hci_cmd_task: hci0 command tx timeout
[ 631.229600] hci_cmd_task: hci0 command tx timeout
[ 636.233411] hci_cmd_task: hci0 command tx timeout
[ 641.236840] hci_cmd_task: hci0 command tx timeout
[ 646.240443] hci_cmd_task: hci0 command tx timeout
[ 651.266419] hci_cmd_task: hci0 command tx timeout

$sudo hcitool inq
Inquiring ...
Inquiry failed.: Connection timed out

* again :
sudo hcitool inq[sudo] password for aslan:
Inquiring ...
* And ctrl+C to kill this process
* then :
sudo hcitool inq
Inquiring ...
 00:05:C9:XX:XX:XX clock offset: 0x4d54 class: 0x520204
 00:1B:59:XX:XX:XX clock offset: 0x54c6 class: 0x5a0204
Alleluia !

Only then, with bluetooth applet, I 'm able to detect new device, attemps to setup my phone is failed ( no any message on my phone ).

After some test on dmesg :

[ 1487.581866] ------------[ cut here ]------------
[ 1487.581880] WARNING: at /build/buildd/linux-2.6.27/fs/sysfs/dir.c:463 sysfs_add_one+0x4e/0x50()
[ 1487.581888] sysfs: duplicate filename 'hci0:6' can not be created
[ 1487.581893] Modules linked in: btusb binfmt_misc af_packet rfkill_input sbs sbshc container pci_slot sco bridge stp bnep rfcomm l2cap bluetooth vboxnetflt vboxdrv ppdev powernow_k8 cpufreq_userspace cpufreq_conservative cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table ipt_REJECT ipt_LOG xt_limit ipt_addrtype xt_state xt_tcpudp xt_conntrack ip6_tables nf_conntrack_netbios_ns nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables sbp2 parport_pc lp parport joydev arc4 ecb crypto_blkcipher snd_hda_intel b43 snd_pcm_oss rfkill snd_mixer_oss snd_pcm mac80211 serio_raw uvcvideo psmouse snd_seq_dummy pcspkr cfg80211 evdev snd_seq_oss compat_ioctl32 videodev v4l1_compat led_class snd_seq_midi snd_rawmidi snd_seq_midi_event input_polldev snd_seq snd_timer snd_seq_device video output snd ricoh_mmc soundcore sdhci_pci sdhci k8temp mmc_core wmi battery ac button nvidia(P) snd_page_alloc agpgart shpchp i2c_nforce2 pci_hotplug i2c_core ext3 jbd mbcache sr_mod cdrom sd_mod crc_t10dif sg usbhid hid pata_amd sata_nv pata_acpi forcedeth ohci1394 ieee1394 ata_generic ssb ehci_hcd libata ohci_hcd scsi_mod dock usbcore thermal processor fan fbcon tileblit font bitblit softcursor fuse
[ 1487.582143] Pid: 5553, comm: btaddconn Tainted: P 2.6.27-9-generic #1
[ 1487.582153] [<c0131d65>] warn_slowpath+0x65/0x90
[ 1487.582168] [<c0253600>] ? vsnprintf+0x400/0x7b0
[ 1487.582181] [<c024d9ca>] ? idr_get_empty_slot+0xda/0x250
[ 1487.582192] [<c024dbc4>] ? ida_get_new_above+0x84/0x1c0
[ 1487.582202] [<c01ffc38>] ? sysfs_ilookup_test+0x8/0x20
[ 1487.582212] [<c01c7286>] ? find_inode+0x46/0x70
[ 1487.582223] [<c01ffc30>] ? sysfs_ilookup_test+0x0/0x20
[ 1487.582233] [<c01ffc30>] ? sysfs_ilookup_test+0x0/0x20
[ 1487.582242] [<c01c6a59>] ? __iget+0x9/0x60
[ 1487.582252] [<c02541f2>] ? strcmp+0x12/0x40
[ 1487.582262] [<...

Read more...

Revision history for this message
Akdo (menoft) wrote :

Oh I'm on intrepid 32 bit up to date.

Revision history for this message
Jeff (jeffmart) wrote :

Ok. Another "same-here". I tried everything. Downgrade bluez4 to bluez3 (hardy repositories). Compile bluez4 from source. Downgrade openobex (and obex* packages). But nothing: no bluetooth common functions.

I am using Ubuntu 8.10, but with kde4 (without kubuntu-desktop package. I have my own desktop config). In some combination, like using all packages from launchpad/blueman repositories and bluetooth-applet running despite kdebluetooth4, I got pairing working well. But just it.

No sending or receiving files nor all other (headsets, bluetooth modem...). And I suspect that problem
is bluetooth stack, because I had this behavior after a upgrade in another machine, that was running
OpenSUSE 11.1. After a bluetooth stack update, tilt! But then I did not pay attention...

What really is desperate-me is the fact that bluetooth is completely broke in Intrepid, for some comments in other forums/lists, too in jaunty, in another dists, but nobody (understanding: developers) is commenting many about...

Revision history for this message
VladimirCZ (vlabla) wrote :

It looks like the problem will be sooner fixed with the new kernel in Jaunty than by some patch.
Pls, see to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.