Pairing a bluetooth device hangs a computer

Bug #211157 reported by Denys Rtveliashvili
34
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez-utils (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have tried to install Ubuntu 8.04 before the release and here is a problem I see: pairing my phone via bluetooth hangs the computer completely.

The bug reproduces every time I do the following:

- I try to pair my phone (NEC e949) to my computer, pairing is initiated from the phone.
- Phone asks for a PIN and I tell it "1234"
- Computer says "Pairing request.."
- I click "Enter passkey" and enter the same PIN in the dialog. And I press "OK"
- Ubuntu says "Created bonding ..."

After that the mouse cursor is frozen, keyboard does not work and the "caps lock" indicator is blinking.

Hardware: Lenovo Thinkpad T61.

Note: This bug reproduces only on an installed Ubuntu 8.04 with all the patches installed. The LiveCD works just fine.

I would be happy to do more research into this but at this point of time I do not know what can be done. The /var/log/messages does not show anything interesting. Perhaps, that's because the computer freezes so quickly that the messages do not get onto disk. By the way, there are numerous messages about transactions being replayed during the ReiserFS's file system check.

I suspect that the problem can be caused either by one of the software updates or a conflict of drivers. The LiveCD obviously does not have nVidia's proprietary driver and there can be other differences too.

One more thing. There is a bug #103365 which looks a bit similar. The difference is that in my case the computer hangs exactly after the pairing.

Revision history for this message
Denys Rtveliashvili (rtvd) wrote :

Now I believe this is something related to IRQ.

When I change the IRQ settings in BIOS from "11" (the factory default) to "Auto" this symptom disappear.

Revision history for this message
Andrew Fenn (andrewfenn) wrote :

I am using a Samsung R55 with Ubuntu 8.04 and I am having the same problems. Nothing about IRQ in my BIOS settings.

Revision history for this message
Kevin Farley (kfarley) wrote :

I just encountered this same kind of lockup today. I have tried 2 different phones in combination with 2 different bluetooth adapters. The lockup only occurs on one of the phones, the HTC Tilt - AT&T 8925 (Win Mobile). The Sony Ericsson (Symbian) phone does not have this problem.

When I initiate bonding from the desktop, no problems. Can connect and browse the device. When I initiate bonding from the HTC Tilt, the system immediately and complete freezes everything.

I tried to catch an error message. I left open two terminal windows, one tailing /var/log/messages and the other tailing /var/log/dmesg and I initiated bonding from the HTC Tilt. It bonded then locked and there were no log messages issued. And when I reboot. There is no record of any errors that I can find.

It doesn't matter what preferences or services I have enabled on the Bluetooth Applet (0.25) the result is the same.

Using Ubuntu Hardy 8.04, kernel 2.6.24-16-generic, gnome 2.22.1 with all latest patches on Athlon machine with 512 MB RAM (non-descript e-machine).

Bluetooth devices: no-name class 1 device and IOgear gbu221 (class 2).

Phones: HTC Tilt - AT&T 8925 (Win Mobile) <- the problem phone and Sony Ericsson (Symbian) <- the no problem phone.

This is NOT a random lockup. It happens every single time I initiate bonding from the HTC Tilt and the lockup occurs immediately after "bonding completed" message displays.

Revision history for this message
felipeDimmu (felipe-dimmu) wrote :

Have the same problem over here...pairing freezes everything and Caps,Num and Scroll lock keep blinking...
Denys Rtveliashvili said something about IRQ, make sense. Maybe Ubuntu/Bluetooth/Linux is trying to use an bad IRQ for pairing? Is there anyway to set which IRQ pairing will use?
Maybe a patch to probe for a proper one?

Cellphone: Motorola A1200i
Notebook: Asus G1S
OS: Hardy 2.6.24-17-generic

Revision history for this message
Pär Bohrarper (par-bohrarper) wrote :

I get the same problem on a Sony Ericsson C702.

Revision history for this message
Alan Hartless (harty83) wrote :

I have this exact problem pairing my compaq presario v3000 and my tilt (htc 8925). I have all the latest updates installed for Hardy. This sucks!

Revision history for this message
vikhyath (vikhyath-gmail) wrote :

Exact same problem for me as well. Please let me know what I can do to help solve this bug.

Cellphone: Motorola A1200R
Notebook: Dell Inspiron 9300
OS: Hardy 2.6.24-18-generic

Revision history for this message
RTSAnime (rtsanime) wrote :

Exact same problem on 2 of my laptops

Cellphone: LG CU720 (tested with both laptops)
Notebook1: Dell Vostro 1400 - Hardy 2.6.24.19-generic
Notebook2: Thinkpad T60p - Hardy 2.6.24.19-generic

Revision history for this message
RTSAnime (rtsanime) wrote :

An Update: Initiating pairing from computer seemed to work on my t60p. Phone and computer are now paired no crash:
From bluetooth menu choose browse device.
Select phone.
enter passkey on both.
pairing goes through no crash.

Will try similar procedure on my Vostro later

Revision history for this message
RTSAnime (rtsanime) wrote :

Worked for my Vostro as well.

Revision history for this message
Simeon Walker (simbloke) wrote :

Same problem with LG KU990 Viewty, pairing initiated from the phone.

Laptop: HP 6510b, Intel chipset, built-in bluetooth
Desktop: Intel DQ35JO motherboard, Belkin USB bluetooth

No problem with other phones: Nokia N95 8GB, Samsun U600, Sony Ericsson K750i.

Revision history for this message
vasilis34 (vmanolop) wrote :

Pairing my laptop (Ubuntu Hardy 8.04) with Sony Ericsson C702 makes the cellphone restart. I have tried all the different combination such as initiating the pairing from the laptop or the phone but always the same problem.

Revision history for this message
Jamie Bullock (jamie-postlude) wrote :

Same problem here:

Ubuntu Hardy 8.04, Ericsson C902

Initiating pairing from phone crashes the laptop
Initiating pairing from the laptop causes a soft reboot of the phone

However, pairing works fine with other phones e.g. Ericsson w810i

Changed in bluez-utils:
status: New → Confirmed
Revision history for this message
Lembitu Ling (snakeman) wrote :

Confirmed pairing with SE C702 crashes cellphone (soft reboot).

Revision history for this message
bjd (bjd-xs4all) wrote :

Me too.

Sony/Ericsson Z600
Standard PC
Ubuntu Hardy 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 GNU/Linux

bjd

Revision history for this message
Alex Filonov (alextcs) wrote :

IBM Thinkpad t41
Palm TX
Latest update of all packages as of today.

Bluetooth worked on this laptop with no problems under Dapper.

Revision history for this message
Karol „Zal” Zalewski (kzzalews) wrote :

ThinkPad R61i & Sony Ericsson C702

Ubuntu 8.04: mouse cursor is frozen, keyboard does not work and the "caps lock" indicator is blinking.

Ubuntu 8.10: soft reboot of cell phone.

Revision history for this message
rudinger (vjorda) wrote :

Standard PC & Sony Ericsson V640i

Ubuntu 8.04: mouse cursor is frozen, keyboard doesnt work and the caps lock indicator is blinking.
Ubuntu 8.10: it works fine.

Revision history for this message
Florian Demmer (fdemmer) wrote :

MSI BlueToe & SE C702, 8.10

strangely this has worked yesterday. i could browse files via nautilus and send files from phone to pc.
today browsing causes a reboot of the phone and the pc is not found when trying to send files.

pairing goes through (initiated from pc, enter passcode, success, ...), but then again reboots or pc not found.

in case it's due to a recent update my updates from yesterday evening (after it had worked):
Commit Log for Mon Nov 10 20:05:54 2008

Upgraded the following packages:
banshee (1.2.1-3ubuntu1) to 1.4.0.1-1~intrepid1
f-spot (0.5.0.3-0ubuntu2) to 0.5.0.3-0ubuntu4
gedit (2.24.0-0ubuntu1) to 2.24.1-0ubuntu1
gedit-common (2.24.0-0ubuntu1) to 2.24.1-0ubuntu1
gnome-panel (1:2.24.1-0ubuntu2) to 1:2.24.1-0ubuntu2.1
gnome-panel-data (1:2.24.1-0ubuntu2) to 1:2.24.1-0ubuntu2.1
jockey-common (0.5~beta3-0ubuntu5) to 0.5~beta3-0ubuntu6
jockey-gtk (0.5~beta3-0ubuntu5) to 0.5~beta3-0ubuntu6
libasound2-plugins (1.0.17-0ubuntu4) to 1.0.17-0ubuntu5
libglib2.0-0 (2.18.2-0ubuntu1) to 2.18.2-0ubuntu2
libglib2.0-dev (2.18.2-0ubuntu1) to 2.18.2-0ubuntu2
libgnome-pilot2 (2.0.15-2ubuntu3) to 2.0.15-2ubuntu4
libgtksourceview2.0-0 (2.4.0-0ubuntu1) to 2.4.1-0ubuntu1
libgtksourceview2.0-common (2.4.0-0ubuntu1) to 2.4.1-0ubuntu1
libpam-modules (1.0.1-4ubuntu5) to 1.0.1-4ubuntu5.2
libpam-runtime (1.0.1-4ubuntu5) to 1.0.1-4ubuntu5.2
libpam0g (1.0.1-4ubuntu5) to 1.0.1-4ubuntu5.2
libpanel-applet2-0 (1:2.24.1-0ubuntu2) to 1:2.24.1-0ubuntu2.1
libpango1.0-0 (1.22.1-0ubuntu1) to 1.22.2-0ubuntu1
libpango1.0-common (1.22.1-0ubuntu1) to 1.22.2-0ubuntu1
libpango1.0-dev (1.22.1-0ubuntu1) to 1.22.2-0ubuntu1
libvolume-id0 (124-8) to 124-9
pm-utils (1.1.2.4-1ubuntu7) to 1.1.2.4-1ubuntu8
udev (124-8) to 124-9
update-manager (1:0.93.32) to 1:0.93.34
update-manager-core (1:0.93.32) to 1:0.93.34
xserver-xorg-input-evdev (1:2.0.99+git20080912-0ubuntu5) to 1:2.0.99+git20080912-0ubuntu6
xserver-xorg-input-vmmouse (1:12.5.1-1ubuntu5) to 1:12.5.1-1ubuntu5.1

where are the logs for all the bt stuff?!

Revision history for this message
Florian Demmer (fdemmer) wrote :

just got this in dmesg, after trying to browse the previously paired phone:

[ 129.811467] type=1503 audit(1226420625.768:5): operation="inode_permission" requested_mask="r::" denied_mask="r::" fsuid=7 name="/proc/6724/net/" pid=6724 profile="/usr/sbin/cupsd"
[ 131.081733] type=1503 audit(1226420627.040:6): operation="inode_permission" requested_mask="r::" denied_mask="r::" fsuid=7 name="/proc/6729/net/" pid=6729 profile="/usr/sbin/cupsd"
[ 131.083138] type=1503 audit(1226420627.040:7): operation="socket_create" family="ax25" sock_type="dgram" protocol=0 pid=6729 profile="/usr/sbin/cupsd"
[ 131.084263] type=1503 audit(1226420627.044:8): operation="socket_create" family="netrom" sock_type="seqpacket" protocol=0 pid=6729 profile="/usr/sbin/cupsd"
[ 131.085434] type=1503 audit(1226420627.044:9): operation="socket_create" family="rose" sock_type="dgram" protocol=0 pid=6729 profile="/usr/sbin/cupsd"
[ 131.086553] type=1503 audit(1226420627.044:10): operation="socket_create" family="ipx" sock_type="dgram" protocol=0 pid=6729 profile="/usr/sbin/cupsd"
[ 131.087675] type=1503 audit(1226420627.044:11): operation="socket_create" family="appletalk" sock_type="dgram" protocol=0 pid=6729 profile="/usr/sbin/cupsd"
[ 131.088847] type=1503 audit(1226420627.048:12): operation="socket_create" family="econet" sock_type="dgram" protocol=0 pid=6729 profile="/usr/sbin/cupsd"
[ 131.089980] type=1503 audit(1226420627.048:13): operation="socket_create" family="ash" sock_type="dgram" protocol=0 pid=6729 profile="/usr/sbin/cupsd"
[ 131.091098] type=1503 audit(1226420627.048:14): operation="socket_create" family="x25" sock_type="seqpacket" protocol=0 pid=6729 profile="/usr/sbin/cupsd"
[ 132.184100] ppdev0: registered pardevice
[ 132.232037] ppdev0: unregistered pardevice

timestamp 131 is definetly when the phone is already rebooting.

Revision history for this message
Richard Marks (w1nt0p) wrote :

OS: Ubuntu Hardy 8.04 64-bit
Cell Phone: LG CU515
BT Adapter: CompUSA Bluetooth adapter P/N: UBTBR1E-N-WWM S/N: 05092701361

Trying to pair my phone, and immediately after I enter the PIN # or freezes the machine, leaving all the blue LEDs on my computer blinking like a retarded display in a retail store.

I really hope there is a fix for this, because I hate to have to reboot into vista just to copy photos from my phone.

Revision history for this message
vikhyath (vikhyath-gmail) wrote :

any updates on this bug? Is it fixed in Jaunty?

Revision history for this message
sles (slesru) wrote :

The same problem with 8.04 and
2.6.24-24-generic #1 SMP Wed Apr 15 15:11:35 UTC 2009 x86_64 GNU/Linux

and wm5 mobile phone
Is there fix?

Revision history for this message
Josiah Yoder (yoder2) wrote :

I had a similar problem the second time I tried to connect to my phone. Every time I typed the four-digit pin on both the phone and the computer, it would connect and then immediately hang. I ended up not connecting with the bluetooth panel applet, and proceeding straight to the following commands. Perhaps it is somehow still connected despite rebooting?

#!/bin/sh
ADDRESS=00:19:A0:A2:70:55
sudo hcitool cc $ADDRESS &&
sudo hcitool auth $ADDRESS &&
( sudo rfcomm connect 0 $ADDRESS 16 </dev/null >/dev/null & )
sleep 2
sudo chmod 666 /dev/rfcomm0

which worked, even though it was a bit finicky.

Revision history for this message
penalvch (penalvch) wrote :

Denys Rtveliashvili, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/211157/comments/1 regarding this being fixed by adjusting your BIOS. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in bluez-utils (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
felipeDimmu (felipe-dimmu) wrote : Re: [Bug 211157] Re: Pairing a bluetooth device hangs a computer

Uowww that was quick.
Em 12/12/2014 03:35, "Christopher M. Penalver" <
<email address hidden>> escreveu:

> Denys Rtveliashvili, this bug report is being closed due to your last
> comment https://bugs.launchpad.net/ubuntu/+source/bluez-
> utils/+bug/211157/comments/1 regarding this being fixed by adjusting
> your BIOS. For future reference you can manage the status of your own
> bugs by clicking on the current status in the yellow line and then
> choosing a new status in the revealed drop down box. You can learn more
> about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you
> again for taking the time to report this bug and helping to make Ubuntu
> better. Please submit any future bugs you may find.
>
> ** Changed in: bluez-utils (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/211157
>
> Title:
> Pairing a bluetooth device hangs a computer
>
> Status in bluez-utils package in Ubuntu:
> Invalid
>
> Bug description:
> I have tried to install Ubuntu 8.04 before the release and here is a
> problem I see: pairing my phone via bluetooth hangs the computer
> completely.
>
> The bug reproduces every time I do the following:
>
> - I try to pair my phone (NEC e949) to my computer, pairing is initiated
> from the phone.
> - Phone asks for a PIN and I tell it "1234"
> - Computer says "Pairing request.."
> - I click "Enter passkey" and enter the same PIN in the dialog. And I
> press "OK"
> - Ubuntu says "Created bonding ..."
>
> After that the mouse cursor is frozen, keyboard does not work and the
> "caps lock" indicator is blinking.
>
> Hardware: Lenovo Thinkpad T61.
>
> Note: This bug reproduces only on an installed Ubuntu 8.04 with all
> the patches installed. The LiveCD works just fine.
>
> I would be happy to do more research into this but at this point of
> time I do not know what can be done. The /var/log/messages does not
> show anything interesting. Perhaps, that's because the computer
> freezes so quickly that the messages do not get onto disk. By the way,
> there are numerous messages about transactions being replayed during
> the ReiserFS's file system check.
>
> I suspect that the problem can be caused either by one of the software
> updates or a conflict of drivers. The LiveCD obviously does not have
> nVidia's proprietary driver and there can be other differences too.
>
> One more thing. There is a bug #103365 which looks a bit similar. The
> difference is that in my case the computer hangs exactly after the
> pairing.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/211157/+subscriptions
>

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.