* [Bluez-devel] L2CAP: ECONNRESET
@ 2006-12-12 17:06 Lukas Szemla
2006-12-12 17:58 ` Marcel Holtmann
0 siblings, 1 reply; 2+ messages in thread
From: Lukas Szemla @ 2006-12-12 17:06 UTC (permalink / raw)
To: bluez-devel
Hi *,
I have a problem with BlueZ when used with openOBEX. I've implemented
application for vCard receiving and every time the vCard is received,
the error on L2CAP level is signalled. This error takes place after the
vCard is sucessfully received (and no error on OBEX level is signaled to
me).
The error is ECONNRESET and is a result of
l2cap_chan_del(sk, ECONNRESET) call
in
l2cap_disconnect_req
This is called from l2cap_sig_channel after device sent
L2CAP_DISCONN_REQ on 0x001 CID channel.
My question is why is the l2cap_chan_del(sk, ECONNRESET) is hard-wired
in L2CAP_DISCONN_REQ request handling? Where is the problem and how can
I get rid of it (on the OBEX level)? Should I never get
L2CAP_DISCONN_REQ in normal operation mode?
I've tried several devices with the same result. My openOBEX is of 1.3,
kernel 2.4.31 official one. I run the application on MIPS.
I've added some traces in the kernel and I can post it here if somebody
finds this useful. I haven't done it now since this is a lot of bloody
stuff that is not the official one.
Any hint is greatly welcomed.
Thanks in advance!
--
Best regards.
LS.
-------------------------------------------------------------------------
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bluez-devel] L2CAP: ECONNRESET
2006-12-12 17:06 [Bluez-devel] L2CAP: ECONNRESET Lukas Szemla
@ 2006-12-12 17:58 ` Marcel Holtmann
0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2006-12-12 17:58 UTC (permalink / raw)
To: BlueZ development
Hi Lukas,
> I have a problem with BlueZ when used with openOBEX. I've implemented
> application for vCard receiving and every time the vCard is received,
> the error on L2CAP level is signalled. This error takes place after the
> vCard is sucessfully received (and no error on OBEX level is signaled to
> me).
>
> The error is ECONNRESET and is a result of
> l2cap_chan_del(sk, ECONNRESET) call
> in
> l2cap_disconnect_req
> This is called from l2cap_sig_channel after device sent
> L2CAP_DISCONN_REQ on 0x001 CID channel.
>
> My question is why is the l2cap_chan_del(sk, ECONNRESET) is hard-wired
> in L2CAP_DISCONN_REQ request handling? Where is the problem and how can
> I get rid of it (on the OBEX level)? Should I never get
> L2CAP_DISCONN_REQ in normal operation mode?
> I've tried several devices with the same result. My openOBEX is of 1.3,
> kernel 2.4.31 official one. I run the application on MIPS.
you should start using a 2.6 kernel. The 2.4 series is not really
supported anymore.
And run "hcidump -X -V" to see what actually happens.
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-12-12 17:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-12-12 17:06 [Bluez-devel] L2CAP: ECONNRESET Lukas Szemla
2006-12-12 17:58 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox