#588250 bluetoothd uses ioctl which does not exist in mainline kernels

Package:
bluez
Source:
bluez
Description:
Bluetooth tools and daemons
Submitter:
Jö Fahlke
Date:
2011-08-18 14:57:04 UTC
Severity:
normal
#588250#5
Date:
2010-07-06 13:54:10 UTC
From:
To:
From /var/log/syslog:
======================================================================
Jul  6 13:56:51 paranoia kernel: [255291.657593] usb 2-1.3: new full speed USB device using uhci_hcd and address 51
Jul  6 13:56:51 paranoia kernel: [255291.790372] usb 2-1.3: New USB device found, idVendor=413c, idProduct=8160
Jul  6 13:56:51 paranoia kernel: [255291.790375] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul  6 13:56:51 paranoia kernel: [255291.790378] usb 2-1.3: Product: Dell Wireless 365 Bluetooth Module
Jul  6 13:56:51 paranoia kernel: [255291.790380] usb 2-1.3: Manufacturer: Dell Computer Corp
Jul  6 13:56:51 paranoia kernel: [255291.790482] usb 2-1.3: configuration #1 chosen from 1 choice
Jul  6 13:56:51 paranoia bluetoothd[24030]: HCI dev 0 registered
Jul  6 13:56:51 paranoia bluetoothd[24030]: HCI dev 0 up
Jul  6 13:56:51 paranoia bluetoothd[24030]: Starting security manager 0
Jul  6 13:56:51 paranoia bluetoothd[24030]: ioctl(HCIUNBLOCKADDR): Invalid argument (22)
Jul  6 13:56:51 paranoia bluetoothd[24030]: Adapter /org/bluez/24030/hci0 has been enabled
Jul  6 13:56:51 paranoia kernel: [255292.142195] ioctl32(bluetoothd:24030): Unknown cmd fd(25) cmd(400448e7){t:'H';sz:4} arg(ff988512) on socket:[3009412]
======================================================================

This appears to happen since my last upgrade, which updated some
bluetooth-related packages:
======================================================================
[AKTUALISIERUNG] bluetooth 4.63-2 -> 4.66-1
[AKTUALISIERUNG] bluez 4.63-2 -> 4.66-1
[AKTUALISIERUNG] bluez-alsa 4.63-2 -> 4.66-1
[AKTUALISIERUNG] bluez-cups 4.63-2 -> 4.66-1
[AKTUALISIERUNG] bluez-gstreamer 4.63-2 -> 4.66-1
[AKTUALISIERUNG] bluez-hcidump 1.42-1+b1 -> 1.42-2
[AKTUALISIERUNG] libbluetooth3 4.63-2 -> 4.66-1
======================================================================
("AKTUALISIERUNG" is german for "update" or "upgrade")

I suspect that the 32bit compatibility layer of the 64bit kernel is missing
some system call used by the new bluetoothd.

Thanks,
Jö.
#588250#18
Date:
2010-07-07 00:01:45 UTC
From:
To:
[...]

No, this is an ioctl which doesn't exist at all in the  mainline kernel.

Ben.
#588250#23
Date:
2010-08-05 07:21:04 UTC
From:
To:
tags 588250 moreinfo
thanks

Hi,

Is the message of this output at the time of start already?

Best regards,
  Nobuhiro
#588250#30
Date:
2011-08-18 14:50:21 UTC
From:
To:
Hi,

I have the same Problem.

I installed the Debian Squeeze on a Playstation3 (powerpc architecture). All my
attempts for using the Logitech bluetooth keyboard mediaboard pro failed. I
found that there is the same similar error reported by bluetoothd:

result of dmesg | grep -e "bluetooth":

[   20.882315] ioctl32(bluetoothd:1052): Unknown cmd fd(25)
cmd(800448e7){t:'H';sz:4} arg(ffaad980) on socket:[4270]

result of cat /var/log/daemon.log | grep -e "bluetooth":

Aug 18 15:50:30 PlayStation3 bluetoothd[1052]: Bluetooth deamon 4.66
Aug 18 15:50:30 PlayStation3 bluetoothd[1052]: Starting SDP server
Aug 18 15:50:31 PlayStation3 bluetoothd[1052]: Starting experimental netlink
support
Aug 18 15:50:31 PlayStation3 bluetoothd[1052]: Failed to find Bluetooth netlink
family
Aug 18 15:50:31 PlayStation3 bluetoothd[1052]: Failed to init netlink plugin
Aug 18 15:50:31 PlayStation3 bluetoothd[1052]: bridge pan0 created
Aug 18 15:50:31 PlayStation3 bluetoothd[1052]: HCI dev 0 registered
Aug 18 15:50:31 PlayStation3 bluetoothd[1052]: HCI dev 0 up
Aug 18 15:50:31 PlayStation3 bluetoothd[1052]: Starting security manager 0
Aug 18 15:50:31 PlayStation3 bluetoothd[1052]: ioctl(HCIUNBLOCKADDR): Invalid
argument (22)
Aug 18 15:50:31 PlayStation3 bluetoothd[1052]: Adapter /org/bluez/1052/hci0 has
been enabled
Aug 18 15:50:31 PlayStation3 bluetoothd[1052]: Failed to access HAL

I can pair the keyboard, but no device is created under /dev/input. I know that
the link between the keyboard and the PS3 onboard Bluetooth is created because
the hcidump command show data transfert.

result of hcidump -X when pressing key ou button pad:

HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
    L2CAP(d): cid 0x0041 len 10 [psm 0]
      0000: a1 01 00 00 14 00 00 00  00 00                    ..........
  0000: c3 00 00 0d 00 27 00 0d  10 00 00 2b 00 18 00 00  .....'.....+....
  0010: 00 01 00 01 00 ff ff 00  00 33 97                 .........3.
    L2CAP(d): cid 0x0041 len 10 [psm 0]
      0000: a1 01 00 00 00 00 00 00  00 00                    ..........
    L2CAP(d): cid 0x0041 len 10 [psm 0]
      0000: a1 01 00 00 1a 00 00 00  00 00                    ..........
    L2CAP(d): cid 0x0041 len 10 [psm 0]
      0000: a1 01 00 00 00 00 00 00  00 00                    ..........
    L2CAP(d): cid 0x0041 len 9 [psm 0]
      0000: a1 02 01 00 00 00 00 00  00                       .........
    L2CAP(d): cid 0x0041 len 9 [psm 0]
      0000: a1 02 00 00 00 00 00 00  00                       .........
  0000: c3 00 00 0d 00 28 00 0d  10 00 00 2b 00 18 00 00  .....(.....+....
  0010: 00 01 00 01 00 ff ff 00  00 33 97

I supposed then this was a problem with the onboard bluetooth of the ps3 that
was partialy supported. I decided to use an usb bluetooth dongle to see if it
works but the problem is the same, with a different error.

result of lsusb:

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 054c:0267 Sony Corp. Tachikoma Device
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 009: ID 0a5c:2148 Broadcom Corp.
Bus 001 Device 008: ID 0a5c:4503 Broadcom Corp.
Bus 001 Device 007: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface
Subclass)
Bus 001 Device 006: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of
BCM2046 Bluetooth)
Bus 001 Device 005: ID 046d:c503 Logitech, Inc. Cordless Mouse+Keyboard
Receiver
Bus 001 Device 002: ID 05e3:0607 Genesys Logic, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

result of dmesg | grep -e "bluetooth":

[ 2363.213902] ioctl32(bluetoothd:1052): Unknown cmd fd(38)
cmd(800448e7){t:'H';sz:4} arg(ffaad980) on socket:[45439]

result of cat /var/log/daemon.log | grep -e "bluetooth":

Aug 18 16:29:34 PlayStation3 bluetoothd[1052]: HCI dev 1 registered
Aug 18 16:29:34 PlayStation3 bluetoothd[1052]: HCI dev 1 up
Aug 18 16:29:34 PlayStation3 bluetoothd[1052]: Starting security manager 1
Aug 18 16:29:34 PlayStation3 bluetoothd[1052]: ioctl(HCIUNBLOCKADDR): Invalid
argument (22)
Aug 18 16:29:34 PlayStation3 bluetoothd[1052]: Adapter /org/bluez/1052/hci1 has
been enabled
Aug 18 16:29:34 PlayStation3 bluetoothd[1052]: Failed to access HAL

But this dongle with this keyboard works fine under Debian Squeeze AMD64. So,
it works on AMD64, not on PowerPC.

Tell me if you need more infos.

Willy.