From: Warp <warp@adygtelecom.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Mobidick BDU33A + SCO
Date: Sun, 06 Aug 2006 16:19:30 +0400 [thread overview]
Message-ID: <1154866769.3670.9.camel@warptech> (raw)
In-Reply-To: <1154607738.10276.11.camel@warptech>
Hi, all.
I try lokalize problem and i find SIGSEGV into function
hci_usb_send_frame (hci_usb.c) structure skb has invalid pointer! Some
times adapter reinit or kernel going to Ooops... Next i try dont send
packets only receive and problem has gone. Look like problem in write
stream only. I use O_NONBLOCK streams.
Any comments?
Best Regards,
Warp.
On Thu, 2006-08-03 at 16:22, Warp wrote:
> Hi,
>
> I have problem with SCO link over Mobidick BDU33A , after 1-3 minutes
> established connection adapter may restart.
> My configuration:
>
> hciconfig hci0 -a
> hci0: Type: USB
> BD Address: xx:xx:xx:xx:xx:xx ACL MTU: 384:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:101 acl:0 sco:0 events:13 errors:0
> TX bytes:300 acl:0 sco:0 commands:13 errors:0
> Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'Bluez-0'
> Class: 0x200404
> Service Classes: Audio
> Device Class: Audio/Video, Device conforms to the Headset
> profile
> HCI Ver: 2.0 (0x3) HCI Rev: 0x6e6 LMP Ver: 2.0 (0x3) LMP Subver:
> 0x6e6
> Manufacturer: Cambridge Silicon Radio (10)
>
> # hciconfig hci0 revision
> hci0: Type: USB
> BD Address: xx:xx:xx:xx:xx:xx ACL MTU: 384:8 SCO MTU: 64:8
> Build 1766
> Chip version: BlueCore4-External
> Max key size: 56 bit
> SCO mapping: HCI
>
> # hciconfig hci0 voice
> hci0: Type: USB
> BD Address: xx:xx:xx:xx:xx:xx ACL MTU: 384:8 SCO MTU: 64:8
> Voice setting: 0x0060 (Default Condition)
> Input Coding: Linear
> Input Data Format: 2's complement
> Input Sample Size: 16 bit
> # of bits padding at MSB: 0
> Air Coding Format: CVSD
>
>
> Kernel 2.6.17.7 with patch from bluez.org
>
> Latest libs & utils.
>
> Howto fix this problem?
>
> Best Reagrds,
> Warp.
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-08-06 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 12:22 [Bluez-devel] Mobidick BDU33A + SCO Warp
2006-08-06 12:19 ` Warp [this message]
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=1154866769.3670.9.camel@warptech \
--to=warp@adygtelecom.com \
--cc=bluez-devel@lists.sourceforge.net \
/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