linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sharmila Prabhu Baila <bp.sharmila@globaledgesoft.com>
To: linux-bluetooth-owner@vger.kernel.org
Cc: jwboyer@kernel.org, linux-bluetooth@vger.kernel.org,
	Marcel Holtmann <marcel@holtmann.org>,
	brian gix <brian.gix@intel.com>
Subject: Issue with Discovery Start
Date: Wed, 2 May 2018 08:09:00 +0530 (IST)	[thread overview]
Message-ID: <568444639.5622951.1525228740086.JavaMail.zimbra@globaledgesoft.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3092 bytes --]

Hi, 

I faced issue during discovery start in both bluez-5.41 and 5.49. Please find the attached logs and help me to resolve this issue. 


bluetoothd[846]: src/adapter.c:stop_discovery() sender :1.2 
bluetoothd[846]: src/adapter.c:discovery_destroy() owner :1.2 
bluetoothd[846]: src/device.c:device_set_rssi_with_delta() rssi 0 
bluetoothd[846]: src/device.c:device_set_tx_power() tx_power 127 
bluetoothd[846]: src/device.c:device_set_rssi_with_delta() rssi 0 
bluetoothd[846]: src/adapter.c:stop_discovery_complete() status 0x0a 
bluetoothd[846]: src/adapter.c:remove_temp_devices() /org/bluez/hci0 
bluetoothd[846]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_00_EC_0A_0F_3A_B2 
bluetoothd[846]: src/device.c:btd_device_unref() Freeing device /org/bluez/hci0/dev_00_EC_0A_0F_3A_B2 
bluetoothd[846]: src/device.c:device_free() 0x17cd570 
bluetoothd[846]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_0C_E0_E4_3F_C4_18 
bluetoothd[846]: src/device.c:btd_device_unref() Freeing device /org/bluez/hci0/dev_0C_E0_E4_3F_C4_18 
bluetoothd[846]: src/device.c:device_free() 0x17cec18 
bluetoothd[846]: src/adapter.c:start_discovery() sender :1.2 
bluetoothd[846]: src/adapter.c:update_discovery_filter() 
bluetoothd[846]: src/adapter.c:discovery_filter_to_mgmt_cp() 


>>>>>>>>> Scanning failed >>>>>>>>>>>> 


bluetoothd[846]: src/adapter.c:update_discovery_filter() filters were equal, deciding to not restart the scan. 

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 

bluetoothd[846]: src/adapter.c:start_discovery() sender :1.2 
bluetoothd[846]: src/adapter.c:stop_discovery() sender :1.2 
bluetoothd[846]: src/adapter.c:discovery_destroy() owner :1.2 
bluetoothd[846]: src/adapter.c:stop_discovery_complete() status 0x0b 
bluetoothd[846]: src/adapter.c:start_discovery() sender :1.2 
bluetoothd[846]: src/adapter.c:update_discovery_filter() 
bluetoothd[846]: src/adapter.c:discovery_filter_to_mgmt_cp() 
bluetoothd[846]: src/adapter.c:update_discovery_filter() filters were equal, deciding to not restart the scan. 
bluetoothd[846]: src/adapter.c:stop_discovery() sender :1.2 
bluetoothd[846]: src/adapter.c:discovery_destroy() owner :1.2 
bluetoothd[846]: src/adapter.c:stop_discovery_complete() status 0x0b 


Waiting for response. 

-- 
Regards, 
Sharmila Prabhu 

Disclaimer:- The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. The views expressed in this E-mail message (including the enclosure/(s) or attachment/(s) if any) are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of GlobalEdge. Before opening any mail and attachments please check them for viruses .GlobalEdge does not accept any liability for virus infected mails.

[-- Attachment #2: Type: text/html, Size: 5459 bytes --]

                 reply	other threads:[~2018-05-02  2:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=568444639.5622951.1525228740086.JavaMail.zimbra@globaledgesoft.com \
    --to=bp.sharmila@globaledgesoft.com \
    --cc=brian.gix@intel.com \
    --cc=jwboyer@kernel.org \
    --cc=linux-bluetooth-owner@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).