[Pkg-bluetooth-maintainers] Bug#878181: bluez: same behaviour, invalid packet size
Sebastian Schneider
sepschneider at gmail.com
Mon Oct 23 08:53:00 UTC 2017
Package: bluez
Version: 5.47-1
Followup-For: Bug #878181
Dear Maintainer,
after some updates last weeki(not sure which one) bluetooth is suddenly unstable.
Doens't matter if I use my headset or mouse or both, bt suddenly stops working. Often after a short period of time.
btmon output:
> HCI Event: Vendor (0xff) plen 7 #3 [hci0] 1.859597
Intel Bootup (0x02)
Zero: 0x00
Number of packets: 2
Source: Operational firmware (0x01)
Reset type: Soft software reset (0x02)
Reset reason: System exception (0x05)
DDC status: Persistent RAM (0x02)
> HCI Event: Vendor (0xff) plen 189 #4 [hci0] 1.862589
Intel System Exception (0x29)
invalid packet size
01 00 00 00 00 00 00 00 02 47 01 01 d8 32 01 50 .........G...2.P
b0 b5 0b 00 00 47 01 01 06 00 00 00 00 00 00 00 .....G..........
00 00 00 00 00 00 00 00 ff 93 10 5b f4 8c 2a 36 ...........[..*6
bb f0 75 00 5c 23 01 50 00 40 00 00 00 00 00 00 ..u.\#.P. at ......
00 00 00 00 04 00 00 00 02 00 00 00 05 00 00 00 ................
f8 ff 00 00 fc ff 00 00 f9 ff 00 00 14 00 00 50 ...............P
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 74 18 00 50 ............t..P
f8 ff 00 00 a0 ad 0b 00 74 13 00 50 10 a0 05 00 ........t..P....
a4 fd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
ef ef ef ef ef ef ef ef ef ef ef ef ............
hcidump output:
> ACL data: handle 256 flags 0x02 dlen 11
L2CAP(d): cid 0x0041 len 7 [psm 19]
HIDP: Data: Input report
> ACL data: handle 256 flags 0x02 dlen 11
L2CAP(d): cid 0x0041 len 7 [psm 19]
HIDP: Data: Input report
> ACL data: handle 256 flags 0x02 dlen 11
L2CAP(d): cid 0x0041 len 7 [psm 19]
HIDP: Data: Input report
> HCI Event: Vendor (0xff) plen 7
> HCI Event: Vendor (0xff) plen 189
A quick fix is stopping the bluetooth service and shutdown the hci0 interface, start it again and afterwards start the bluetooth daemon again.
This "fixes" the problem for 0 to 120 seconds.
As this happens with multiple bluetooth devices, which work fine on other computers, I'm pretty sure something broke in bluez.
Best
Sebastian
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages bluez depends on:
ii dbus 1.11.20-1
ii init-system-helpers 1.50
ii kmod 24-1
ii libasound2 1.1.3-5
ii libc6 2.24-17
ii libdbus-1-3 1.11.20-1
ii libdw1 0.170-0.1
ii libglib2.0-0 2.54.1-1
ii libreadline7 7.0-3
ii libudev1 235-2
ii lsb-base 9.20170808
ii udev 235-2
bluez recommends no packages.
Versions of packages bluez suggests:
ii pulseaudio-module-bluetooth 11.1-1
-- no debconf information
More information about the Pkg-bluetooth-maintainers
mailing list