Mailinglist Archive: opensuse-bugs (7462 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=359920


           Summary: event/0 goes into busy loop after removing bluetooth
                    dongle with active rfcomm interface
           Product: openSUSE 11.0
           Version: Alpha 2
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kernel
        AssignedTo: kernel-maintainers@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: seife@xxxxxxxxxx
         QAContact: qa@xxxxxxx
                CC: fseidel@xxxxxxxxxx
          Found By: Development


First: i am not sure if this is related to
https://bugzilla.novell.com/show_bug.cgi?id=359546 or even a duplicate. Some
symptoms are similar (lost keyboard...)

If i remove a bluetooth dongle on which an rfcomm connection is in use, the
event/0 kernel task goes into a busy loop (takes 100% cpu) and the keyboard is
nonfunctional. PS2 mice (IBM trackpoint and synaptics touchpads) still work.
Reproduced on two different machines with different BT dongles. The last thing
in dmesg was "usb disconnect", no bluetooth messages or similar. Also, no oops.

How to reproduce:
- plug in a bluetooth dongle. Make your phone visible on bluetooth.
seife@susi:~> hcitool scan
Scanning ...
        00:12:EE:23:CE:EA       my_phone
seife@susi:~> sdptool browse 00:12:EE:23:CE:EA | grep -A 8 -i dial-up
Service Name: Dial-up Networking
Service RecHandle: 0x10001
Service Class ID List:
  "Dialup Networking" (0x1103)
  "Generic Networking" (0x1201)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 1

"Channel:1" is the important information here.
do (as root):
rfcomm bind rfcomm0 00:12:EE:23:CE:EA 1

you shuld now see this:
root@susi:~# rfcomm
rfcomm0: 00:12:EE:23:CE:EA channel 1 clean

now use this device. Make sure you have kdebluetooth or bluetooth-applet (from
bluez-gnome) running as a passkey-agent.
Do

cat /dev/rfcomm0

On the phone, you should allow usage, a authentication dialog should pop up on
the phone and on the desktop. Enter the same PIN on both dialogs.

Now pull the bluetooth dongle out (or disable bluetooth with a hotkey) and
enjoy the bug. Warning: keyboard will be gone, so you might want to log in via
ssh before trying this to be able to gather information.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.