Date: 29 Nov 2005 02:17:18 +0000 From: faigozhu <faigozhu@fastmail.fm> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. Message-ID: <86ek5019ld.fsf@fastmail.fm> In-Reply-To: <438B9E3E.5020905@savvis.net> References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> <86psok1jl6.fsf@fastmail.fm> <438B9E3E.5020905@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Maksim Yevmenkin <maksim.yevmenkin@savvis.net> writes: > >>> I have a Motorola HS805 headset and got the following > >>> message. #sdpcontrol -a 00:0b:2e:32:65:12 search HSET Could not > >>> execute > >>> command "search". Operation timed out > >> did you try to repeat this command several times? does it always > >> fail with timeout? > > yes. > > ok > > >>> It seems no response from the headset after sending > >>> Link_Key_Reply? > >> sigh... people, please, PLEASE, stop posting text hci dump. they > >> are not very useful. they give me some idea, but what i really need > >> is _binary_ hci dump. > > Sorry for that. The attached file is a binary file of "hcidump -w > hcidump.log". > > thanks. unfortunately, this binary dump did not reveal the > problem. i'd like you to try the following: > > 1) reboot > > 2) attach usb bluetooth dongle and start bluetooth stack # /etc/rc.bluetooth start ubt0 BD_ADDR: 00:0a:3a:63:de:86 Features: 0xff 0xfe 0xd 0x38 0x8 0x8 00 00 <3-Slot> <5-Slot> <Encryption> <Slot offset> <Timing accuracy> <Switch> <Hold mode> <Sniff mode> <RSSI> <Channel quality> <SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD> <Power control> <Transparent SCO data> Max. ACL packet size: 377 bytes Number of ACL packets: 10 Max. SCO packet size: 16 bytes Number of SCO packets: 0 # hcidump -w headset.dump2 HCIDump - HCI packet analyzer ver 1.5 device: any snap_len: 65535 filter: 0xffffffff > > 3) as root > # hcidump -w headset.dump > > 4) as root > # hccontrol -n ubt0hci create_connection 00:0b:2e:32:65:12 > > make sure hccontrol succeeded and created baseband connection. > it should print connection handle. BD_ADDR: 00:0b:2e:32:65:12 Connection handle: 6 Encryption mode: Disabled [0] > > 5) wait a few seconds, and run > % sdpcontrol -a 00:0b:2e:32:65:12 search HSET Could not execute command "search". Operation timed out. > > you may try step 5) a couple more times. please wait few seconds > between each try. still timed out. > > 6) kill hcidump with ^c and send me the headset.dump file > --=-=-= Content-Type: application/octet-stream Content-Disposition: attachment; filename=headset.dump Content-Transfer-Encoding: base64 EQAAAEG1i0M+OQkAAQUEDRJlMi4LABhMAAAAAAEHAAEAQbWLQ7r1CQAEDwQAAQUECQABAES1i0MB VgkABBcGEmUyLgsAGgAAAES1i0OyVgkAAQsEFhJlMi4LACcZINaDEpxA5ufM/wvMH/wNAAEARLWL Qyb2CQAEDgoBCwQAEmUyLgsADgABAES1i0OUtQoABAMLAAYAEmUyLgsAAQAIAAAARLWLQ5i1CgAB DQgEBgAHAAkAAQBEtYtDBskKAAQOBgENCAAGAAYAAQBEtYtDmoQLAAQbAwYABREAAABatYtDYL4A AAIGIAwACAABAAIBBAABAEAACAABAFq1i0Nj7AAABBMFAQYAAQAJAAEAWrWLQ/WjAQAEFwYSZTIu CwAaAAAAWrWLQ4SkAQABCwQWEmUyLgsAJxkg1oMSnEDm58z/C8wf/A0AAQBatYtDibcBAAQOCgEL BAASZTIuCwAHAAAAm7WLQ326AAABBgQDBgATBwABAJu1i0NLVgEABA8EAAEGBAcAAQCbtYtDt2cC AAQFBAAGABY= --=-=-= Content-Type: application/octet-stream Content-Disposition: attachment; filename=headset.dump2 Content-Transfer-Encoding: base64 EQAAAMW2i0MYDwYAAQUEDRJlMi4LABhMAAAAAAEHAAEAxbaLQ6DPBgAEDwQAAQUECQABAMa2i0Np rQAABBcGEmUyLgsAGgAAAMa2i0MIrgAAAQsEFhJlMi4LACcZINaDEpxA5ufM/wvMH/wNAAEAxraL Q5FNAQAEDgoBCwQAEmUyLgsADgABAMa2i0PxDAIABAMLAAYAEmUyLgsAAQAIAAAAxraLQ/MMAgAB DQgEBgAHAAkAAQDGtotDeCACAAQOBgENCAAGAAYAAQDGtotDxzsCAAQbAwYABREAAADStotDmbUF AAIGIAwACAABAAIBBAABAEAACAABANK2i0P24gUABBMFAQYAAQAJAAEA0raLQ4iaBgAEFwYSZTIu CwAaAAAA0raLQxabBgABCwQWEmUyLgsAJxkg1oMSnEDm58z/C8wf/A0AAQDStotDHK4GAAQOCgEL BAASZTIuCwAHAAAAE7eLQ7ayBQABBgQDBgATBwABABO3i0PfTAYABA8EAAEGBAcAAQATt4tDelYH AAQFBAAGABY= --=-=-= > also, i assume, you have paired less then 8 devices with this headset, > correct? yes. >some headsets can only remember one host, but this one seems > to be able to remember up to 8 (according to specs). > > also, if this is not too much trouble, you could reset the headset and > try the steps 1-6 from above again. > > thanks, > max dmesg: ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2 ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new xfer will be submitted! # hcsecd -d hcsecd[626]: Restored link key for the entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805' <hccontrol -n ubt0hci create_connection 00:0b:2e:32:65:12> hcsecd[626]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 hcsecd[626]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists hcsecd[626]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 <running sdpcontrol -a 00:0b:2e:32:65:12 search HSET> hcsecd[626]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 hcsecd[626]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists hcsecd[626]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 Many thanks, Faigozhu --=-=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86ek5019ld.fsf>