You are not logged in.

Pages: 1

#1 2018-06-27 11:17:42

judd1
Member
Registered: 2015-09-04
Posts: 260

[Solved] Bluetooth performance does not match journalctl.

Bluetooth works well and I do not have problems with it, but when I consult journalctl I see too many errors that do not match reality.

If bluetooth is doing its job well, why are so many errors?

$ LANG=C journalctl -p 3 -xb
-- Logs begin at Sun 2018-06-24 09:50:54 -03, end at Wed 2018-06-27 08:03:11 -03. --
Jun 27 05:42:56 arch kernel: usbhid 3-2:1.1: couldn't find an input interrupt endpoint
Jun 27 05:42:58 arch bluetoothd[440]: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 05:42:58 arch bluetoothd[440]: avrcp-controller: Protocol not supported (93)
Jun 27 05:42:58 arch bluetoothd[440]: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 05:42:58 arch bluetoothd[440]: audio-avrcp-target: Protocol not supported (93)
Jun 27 05:43:22 arch systemd-coredump[6317]: Process 6314 (gsettings-helpe) of user 1000 dumped core.
                                             
                                             Stack trace of thread 6314:
                                             #0  0x00007f1efd557ed2 n/a (libglib-2.0.so.0)
                                             #1  0x00007f1efd558f7d g_log_default_handler (libglib-2.0.so.0)
                                             #2  0x00007f1efd55921f g_logv (libglib-2.0.so.0)
                                             #3  0x00007f1efd5593a0 g_log (libglib-2.0.so.0)
                                             #4  0x00007f1efdb843d2 n/a (libgio-2.0.so.0)
                                             #5  0x00007f1efd83259b n/a (libgobject-2.0.so.0)
                                             #6  0x00007f1efd834180 g_object_new_valist (libgobject-2.0.so.0)
                                             #7  0x00007f1efd83450a g_object_new (libgobject-2.0.so.0)
                                             #8  0x000055782999cd01 main (gsettings-helper)
                                             #9  0x00007f1efcf4f06b __libc_start_main (libc.so.6)
                                             #10 0x000055782999ce5a n/a (gsettings-helper)
-- Subject: Process 6314 (gsettings-helpe) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 6314 (gsettings-helpe) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Jun 27 05:43:25 arch bluetoothd[440]: L2CAP server failed for Message Notification: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 05:43:25 arch bluetoothd[440]: L2CAP server failed for Message Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 05:43:25 arch bluetoothd[440]: L2CAP server failed for Phone Book Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 05:43:25 arch bluetoothd[440]: L2CAP server failed for File Transfer: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 05:43:25 arch bluetoothd[440]: L2CAP server failed for Object Push: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 06:05:26 arch bluetoothd[440]: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 06:05:26 arch bluetoothd[440]: avrcp-controller: Protocol not supported (93)
Jun 27 06:05:26 arch bluetoothd[440]: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 06:05:26 arch bluetoothd[440]: audio-avrcp-target: Protocol not supported (93)
Jun 27 06:05:26 arch bluetoothd[440]: L2CAP server failed for Message Notification: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 06:05:26 arch bluetoothd[440]: L2CAP server failed for Message Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 06:05:26 arch bluetoothd[440]: L2CAP server failed for Phone Book Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 06:05:26 arch bluetoothd[440]: L2CAP server failed for File Transfer: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 06:05:26 arch bluetoothd[440]: L2CAP server failed for Object Push: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:36 arch kernel: ERROR @wl_notify_scan_status : 
Jun 27 07:28:37 arch bluetoothd[440]: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: avrcp-controller: Protocol not supported (93)
Jun 27 07:28:37 arch bluetoothd[440]: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: audio-avrcp-target: Protocol not supported (93)
Jun 27 07:28:37 arch bluetoothd[440]: L2CAP server failed for Message Notification: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: L2CAP server failed for Message Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: L2CAP server failed for Phone Book Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: L2CAP server failed for File Transfer: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: L2CAP server failed for Object Push: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
lines 15-53/53 (END)
$ LANG=C systemctl status bluetooth.service
* bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2018-06-27 05:42:58 -03; 2h 23min ago
     Docs: man:bluetoothd(8)
 Main PID: 440 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 4.1M
   CGroup: /system.slice/bluetooth.service
           `-440 /usr/lib/bluetooth/bluetoothd

Jun 27 07:28:37 arch bluetoothd[440]: avrcp-controller: Protocol not supported (93)
Jun 27 07:28:37 arch bluetoothd[440]: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: audio-avrcp-target: Protocol not supported (93)
Jun 27 07:28:37 arch bluetoothd[440]: L2CAP server failed for Message Notification: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: L2CAP server failed for Message Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: L2CAP server failed for Phone Book Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: L2CAP server failed for File Transfer: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: L2CAP server failed for Object Push: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Jun 27 07:28:37 arch bluetoothd[440]: Endpoint registered: sender=:1.13 path=/MediaEndpoint/A2DPSource
Jun 27 07:28:37 arch bluetoothd[440]: Endpoint registered: sender=:1.13 path=/MediaEndpoint/A2DPSink
LANG=C dmesg

https://hastebin.com/raw/mamamaxaba

Last edited by judd1 (2018-06-27 12:26:20)

This isn't right. This isn't even wrong.
-- Wolfgang Pauli --

Offline

#2 2018-06-27 11:43:11

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,728

Re: [Solved] Bluetooth performance does not match journalctl.

These aren't errors that are relevant for you. Bluez queries the connected device for certain aspects of the Bluetooth protocol, returning a failure message for protocols that were reported as unsupported. Unless you expect your headset to have a phone book address or or the ability to transfer files from the aether this is simply informational message that has no relevance to you. If you want to know more about what is happening here I'd guess https://en.wikipedia.org/wiki/List_of_B … _protocols would be a good place to start

Last edited by V1del (2018-06-27 11:55:59)

Offline

#3 2018-06-27 11:56:28

judd1
Member
Registered: 2015-09-04
Posts: 260

Re: [Solved] Bluetooth performance does not match journalctl.

V1del wrote:

These aren't errors that are relevant for you. Bluez queries the connected device for certain aspects of the Bluetooth protocol, returning a failure message for protocols that were reported as unsupported. Unless you expect your headset to have a phone book address or or the ability to transfer files from the aether this is simply informational message that has no relevance to you.

Agreed, it was more or less what he thought, although not with the accuracy of his knowledge.

Thank you for evacuating these doubts and for such a quick response. I'm already reading the bluetooth protocols.

Thank you very much !

My respects.

Last edited by judd1 (2018-06-27 12:00:15)

This isn't right. This isn't even wrong.
-- Wolfgang Pauli --

Offline

Pages: 1

Board footer

Powered by FluxBB