Re: bluez git + Linksys USBBT100 + 2.6.30-rc2 -> Segmentation fault

public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed

From: Stuart Pook <linux-bluetooth4@pook.es>
To: Johan Hedberg <johan.hedberg@gmail.com>,
	BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez git + Linksys USBBT100 + 2.6.30-rc2 -> Segmentation fault
Date: Mon, 20 Apr 2009 19:45:31 +0200	[thread overview]
Message-ID: <49ECB4BB.8050204@pook.es> (raw)
In-Reply-To: <20090419213837.GA6514@jh-x301>

hi Johan

On 19/04/09 23:38, Johan Hedberg wrote:
> Could you please run bluetoothd through valgrind to get a proper 
> backtrace.

I tested the bluetoothd from git and aplay with the alsa libs from bluez 4.36. I ran play 1451 times. It worked once. valgrind didn't say anything. I guess the errors below are more or less normal because my headset's battery went flat. I don't think that the "Too short" message from aplay is normal (even if the headset is off).

Playing WAVE '/home/stuart/ws/music_test/Rebecca_Pidgeon-You_Got_Me-8000-mono.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono
ALSA lib pcm_bluetooth.c:1607:(audioservice_expect) BT_START_STREAM failed : Success(0)
ALSA lib pcm_bluetooth.c:1566:(audioservice_recv) Too short (1 bytes) IPC packet from bluetoothd
aplay: set_params:1022: Unable to install hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 16
CHANNELS: 1
RATE: 8000
PERIOD_TIME: 125000
PERIOD_SIZE: 1000
PERIOD_BYTES: 2000
PERIODS: 4
BUFFER_TIME: 500000
BUFFER_SIZE: 4000
BUFFER_BYTES: 8000
TICK_TIME: [0 0]

bluetoothd[1851]: Unable to get service record: Host is down (112)
bluetoothd[1851]: Unable to get a SCO fd
bluetoothd[1851]: headset_resume_complete: resume failed
bluetoothd[1851]: Audio API: BT_ERROR -> BT_START_STREAM
bluetoothd[1851]: telephony-dummy: device 0x4b90d40 disconnected
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
bluetoothd[1851]: Unix client disconnected (fd=13)
bluetoothd[1851]: Accepted new client connection on unix socket (fd=13)
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_GET_CAPABILITIES
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_GET_CAPABILITIES
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_OPEN
bluetoothd[1851]: open sco - object=ANY source=ANY destination=00:1A:45:2F:49:98 lock=write
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_OPEN
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_SET_CONFIGURATION
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
bluetoothd[1851]: adapter_get_device(00:1A:45:2F:49:98)
bluetoothd[1851]: Unable to get service record: Host is down (112)
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_SET_CONFIGURATION
bluetoothd[1851]: telephony-dummy: device 0x4b90d40 disconnected
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_START_STREAM
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
bluetoothd[1851]: adapter_get_device(00:1A:45:2F:49:98)
bluetoothd[1851]: Unable to get service record: Host is down (112)
bluetoothd[1851]: Unable to get a SCO fd
bluetoothd[1851]: headset_resume_complete: resume failed
bluetoothd[1851]: Audio API: BT_ERROR -> BT_START_STREAM
bluetoothd[1851]: telephony-dummy: device 0x4b90d40 disconnected
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
bluetoothd[1851]: Unix client disconnected (fd=13)
bluetoothd[1851]: Accepted new client connection on unix socket (fd=13)
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_GET_CAPABILITIES
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_GET_CAPABILITIES
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_OPEN
bluetoothd[1851]: open sco - object=ANY source=ANY destination=00:1A:45:2F:49:98 lock=write
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_OPEN
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_SET_CONFIGURATION
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
bluetoothd[1851]: adapter_get_device(00:1A:45:2F:49:98)
bluetoothd[1851]: Unable to get service record: Host is down (112)
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_SET_CONFIGURATION
bluetoothd[1851]: telephony-dummy: device 0x4b90d40 disconnected
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_START_STREAM
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
bluetoothd[1851]: adapter_get_device(00:1A:45:2F:49:98)
bluetoothd[1851]: Unable to get service record: Host is down (112)
bluetoothd[1851]: Unable to get a SCO fd
bluetoothd[1851]: headset_resume_complete: resume failed
bluetoothd[1851]: Audio API: BT_ERROR -> BT_START_STREAM
bluetoothd[1851]: telephony-dummy: device 0x4b90d40 disconnected
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
bluetoothd[1851]: Unix client disconnected (fd=13)
bluetoothd[1851]: Accepted new client connection on unix socket (fd=13)
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_GET_CAPABILITIES
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_GET_CAPABILITIES
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_OPEN
bluetoothd[1851]: open sco - object=ANY source=ANY destination=00:1A:45:2F:49:98 lock=write
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_OPEN
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_SET_CONFIGURATION
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
bluetoothd[1851]: adapter_get_device(00:1A:45:2F:49:98)
bluetoothd[1851]: Unable to get service record: Host is down (112)
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_SET_CONFIGURATION
bluetoothd[1851]: telephony-dummy: device 0x4b90d40 disconnected
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_START_STREAM
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
bluetoothd[1851]: adapter_get_device(00:1A:45:2F:49:98)
bluetoothd[1851]: Unable to get service record: Host is down (112)
bluetoothd[1851]: Unable to get a SCO fd
bluetoothd[1851]: headset_resume_complete: resume failed
bluetoothd[1851]: Audio API: BT_ERROR -> BT_START_STREAM
bluetoothd[1851]: telephony-dummy: device 0x4b90d40 disconnected
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
bluetoothd[1851]: Unix client disconnected (fd=13)
bluetoothd[1851]: Accepted new client connection on unix socket (fd=13)
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_GET_CAPABILITIES
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_GET_CAPABILITIES
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_OPEN
bluetoothd[1851]: open sco - object=ANY source=ANY destination=00:1A:45:2F:49:98 lock=write
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_OPEN
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_SET_CONFIGURATION
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
bluetoothd[1851]: adapter_get_device(00:1A:45:2F:49:98)
bluetoothd[1851]: Unable to get service record: Host is down (112)
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_SET_CONFIGURATION
bluetoothd[1851]: telephony-dummy: device 0x4b90d40 disconnected
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_START_STREAM
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
bluetoothd[1851]: adapter_get_device(00:1A:45:2F:49:98)
bluetoothd[1851]: Unable to get service record: Host is down (112)
bluetoothd[1851]: Unable to get a SCO fd
bluetoothd[1851]: headset_resume_complete: resume failed
bluetoothd[1851]: Audio API: BT_ERROR -> BT_START_STREAM
bluetoothd[1851]: telephony-dummy: device 0x4b90d40 disconnected
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
bluetoothd[1851]: Unix client disconnected (fd=13)
bluetoothd[1851]: Accepted new client connection on unix socket (fd=13)
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_GET_CAPABILITIES
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_GET_CAPABILITIES
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_OPEN
bluetoothd[1851]: open sco - object=ANY source=ANY destination=00:1A:45:2F:49:98 lock=write
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_OPEN
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_SET_CONFIGURATION
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
bluetoothd[1851]: adapter_get_device(00:1A:45:2F:49:98)
bluetoothd[1851]: Unable to get service record: Host is down (112)
bluetoothd[1851]: Audio API: BT_RESPONSE -> BT_SET_CONFIGURATION
bluetoothd[1851]: telephony-dummy: device 0x4b90d40 disconnected
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
bluetoothd[1851]: Audio API: BT_REQUEST <- BT_START_STREAM
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
bluetoothd[1851]: adapter_get_device(00:1A:45:2F:49:98)
bluetoothd[1851]: Unable to get service record: Host is down (112)
bluetoothd[1851]: Unable to get a SCO fd
bluetoothd[1851]: headset_resume_complete: resume failed
bluetoothd[1851]: Audio API: BT_ERROR -> BT_START_STREAM
bluetoothd[1851]: telephony-dummy: device 0x4b90d40 disconnected
bluetoothd[1851]: State changed /org/bluez/1851/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
bluetoothd[1851]: Unix client disconnected (fd=13)



-- 
If the From address bounces, please see http://www.pook.it/.

next prev parent reply	other threads:[~2009-04-20 17:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05 12:02 bluez 4.34 + Linksys USBBT100 + hcitool scan -> core dump Stuart Pook
2009-04-05 17:04 ` Stuart Pook
2009-04-05 17:22   ` Johan Hedberg
2009-04-19 19:19     ` bluez git + Linksys USBBT100 + 2.6.30-rc2 -> Segmentation fault Stuart Pook
2009-04-19 20:05       ` Johan Hedberg
2009-04-19 21:12         ` Stuart Pook
2009-04-19 21:38           ` Johan Hedberg
2009-04-19 22:05             ` Stuart Pook
2009-04-20 17:45             ` Stuart Pook [this message]
2009-04-05 17:19 ` bluez 4.34 + Linksys USBBT100 + hcitool scan -> core dump Johan Hedberg
2009-04-06 21:20   ` Stuart Pook

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=49ECB4BB.8050204@pook.es \
    --to=linux-bluetooth4@pook.es \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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