Your message dated Sat, 17 Aug 2024 17:10:06 +0900
with message-id
<paiyx2gkxi7idbezo4qbg6jbm3ga7c7wxpiqef3nyklpmtbqzn@egd3jbdweioj>
and subject line Close bug
has caused the Debian Bug report #1060224,
regarding bluetoothd started segfaulting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1060224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060224
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bluez
Version: 5.71-1
Severity: normal
On upgrade to this version, bluetoothd started segfaulting frequently:
[ 59.628624] input: Avantree SP750 (AVRCP) as /devices/virtual/input/input26
[ 97.073761] bluetoothd[838]: segfault at 561314652a23 ip 000056167406a375 sp
00007fffb128a200 error 4 in bluetoothd[561674048000+ec000] likely on CPU 11
(core 5, socket 0)
[ 97.073799] Code: 00 31 c0 e9 54 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00
66 90 f3 0f 1e fa 41 55 41 54 55 53 48 83 ec 08 48 8b 2a 48 8b 7a 08 <48> 8b 45
20 4c 8b ad 88 00 00 00 4c 8b 20 48 85 ff 74 19 c7 47 08
[ 219.074962] input: Avantree SP750 (AVRCP) as /devices/virtual/input/input27
[ 241.708695] bluetoothd[4477]: segfault at 55c5369dc8d4 ip 000055c069877375
sp 00007fff8f7198c0 error 4 in bluetoothd[55c069855000+ec000] likely on CPU 0
(core 0, socket 0)
[ 241.708725] Code: 00 31 c0 e9 54 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00
66 90 f3 0f 1e fa 41 55 41 54 55 53 48 83 ec 08 48 8b 2a 48 8b 7a 08 <48> 8b 45
20 4c 8b ad 88 00 00 00 4c 8b 20 48 85 ff 74 19 c7 47 08
To reproduce this crash all I have to do is:
1. connect to the bluetooth device
2. use it briefly
3. stop using it and wait 5 seconds
Based on the timing, the crash probably occurs when it's put into power save
mode.
I have downgraded to 5.70-1.1, which does not have this problem.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.6.9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages bluez depends on:
ii dbus [default-dbus-system-bus] 1.14.10-3+b1
ii init-system-helpers 1.66
ii kmod 31-1
ii libasound2 1.2.10-3
ii libc6 2.37-13
ii libdbus-1-3 1.14.10-3+b1
ii libdw1 0.190-1+b1
ii libglib2.0-0 2.78.3-1
ii libreadline8 8.2-3
ii libudev1 255.2-3
ii udev 255.2-3
bluez recommends no packages.
Versions of packages bluez suggests:
pn pulseaudio-module-bluetooth <none>
-- Configuration Files:
/etc/bluetooth/main.conf changed:
[General]
Experimental = true
[BR]
[LE]
[GATT]
[CSIS]
[AVDTP]
[Policy]
AutoEnable=true
[AdvMon]
-- no debconf information
--
see shy jo
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 5.73-1
This problem has been fixed in 5.73-1.
Therefore, this bug is closed. Thank you for your report.
Best regards,
Nobuhiro
--- End Message ---
