Hi, I guess I'm approaching the same or at least a related problem. I don't feel like getting close the root of the problem yet but maybe the attached output helps marcel or someone else to see clearer. I can't pretend that the reset in the attached log is not beeing sent from a user-application but i felt like the oops is worth posting. Kernel used is 2.6.8.1 but i know that the thing happens also with 2.6.17.6. Hardware used: hci1: Type: USB BD Address: 00:02:5B:00:BF:66 ACL MTU: 384:8 SCO MTU: 64:8 HCI 19.2 Chip version: BlueCore4-ROM Max key size: 128 bit SCO mapping: HCI BD Address: 00:02:5B:00:BF:66 ACL MTU: 384:8 SCO MTU: 64:8 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80 <3-slot packets> <5-slot packets> <3-slot EDR ACL> <5-slot EDR ACL> <3-slot EDR eSCO> I don't expect any feedback on this, I'll post in this thread if I find anything.. Greetings Andy On Fri, 28 Jul 2006 03:56:09 +0200 Marcel Holtmann wrote: > Hi Lan, > > > I try to setup openobex on my linux, but each time I send out obex > > connect request, instead of getting a connect response, the device will > > be reset, HCIDUMP is like below: > > > > ... > > ... > > ... > > > HCI Event: Number of Completed Packets (0x13) plen 5 > > > ACL data: handle 41 flags 0x02 dlen 8 > > L2CAP(d): cid 0x0040 len 4 [psm 3] > > RFCOMM(s): UA: cr 1 dlci 6 pf 1 ilen 0 fcs 0x18 > > < ACL data: handle 41 flags 0x02 dlen 12 > > L2CAP(d): cid 0x0040 len 8 [psm 3] > > RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2 > > dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0 > > > ACL data: handle 41 flags 0x02 dlen 12 > > L2CAP(d): cid 0x0040 len 8 [psm 3] > > RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2 > > dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0 > > < ACL data: handle 41 flags 0x02 dlen 12 > > L2CAP(d): cid 0x0040 len 8 [psm 3] > > RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2 > > dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0 > > > HCI Event: Number of Completed Packets (0x13) plen 5 > > > HCI Event: Number of Completed Packets (0x13) plen 5 > > > ACL data: handle 41 flags 0x02 dlen 12 > > L2CAP(d): cid 0x0040 len 8 [psm 3] > > RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2 > > dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0 > > < ACL data: handle 41 flags 0x02 dlen 9 > > L2CAP(d): cid 0x0040 len 5 [psm 3] > > RFCOMM(d): UIH: cr 1 dlci 6 pf 1 ilen 0 fcs 0x93 credits 33 > > < ACL data: handle 41 flags 0x02 dlen 34 > > L2CAP(d): cid 0x0040 len 30 [psm 3] > > RFCOMM(d): UIH: cr 1 dlci 6 pf 0 ilen 26 fcs 0x8f > > OBEX: Connect cmd(f): len 26 version 1.1 flags 0 mtu 1024 > > Target (0x46) = Sequence length 16 > > < HCI Command: Reset (0x03|0x0003) plen 0 > > > > The system I have is Linux 2.6.9-34, bluez-lib-2.25 and bluez-util-2.25, > > bluez-hcidump-1.30, and openobex-1.0.1 version. I don't know who send > > this reset, and why. > > the reset is really strange. It comes from our side. What does > "hciconfig -a" say about your dongle. > > Regards > > Marcel > > > > ------------------------------------------------------------------------- > 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-users mailing list > Bluez-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluez-users -- -- mit freundlichen Grüßen / best regards, Andreas Gaufer Office: +49 951-700428-91 Fax: +49 951-700428-87 Mail: Andreas.Gaufer@bluecellnetworks.com I fully agree with RFC 1855