thomas.schorpp wrote:
thomas.schorpp wrote:
quoted
hi, yes i read the previous threads, this could be the well known problems with the via usb chips ;), it does not occur with my older p2 machine. linux, pda and window$ clients kill my server after minutes:
^[[AJan 5 21:09:46 TOM1 kernel: hci_acl_tx_to: hci0 ACL tx timeout
Jan 5 21:09:46 TOM1 kernel: hci_acl_tx_to: hci0 killing stalled ACL connection DC:0F:A5:60:10:00
Jan 5 21:22:47 TOM1 pand[5823]: Accept failed. Interrupted system call(4)
Jan 5 21:53:36 TOM1 kernel: hci_acl_tx_to: hci0 ACL tx timeout
Jan 5 21:53:36 TOM1 kernel: hci_acl_tx_to: hci0 killing stalled ACL connection DC:0F:A5:60:10:00
same with the nokia affix stack.
cuurently i run a script detecting this error, resetting the bluetooth and restarting the daemons automatically.
no nice way.
there should be a way to recover that fault better, but where to start?
y
tom
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
pand/main.c/154/nsk = accept(sk, (struct sockaddr *) &l2a, &alen);
synchronous execution stalls next connect... adding a time out and recovery?
wheres the this "accept"() , cant find it in any bt header, need source browser for linux ;)
y
tom
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
aah found it..
/* Await a connection on socket FD.
When a connection arrives, open a new socket to communicate with it,
set *ADDR (which is *ADDR_LEN bytes long) to the address of the connecting
peer and *ADDR_LEN to the address's actual length, and return the
new socket's descriptor, or -1 for errors. */
extern int accept (int __fd, __SOCKADDR_ARG __addr,
socklen_t *__restrict __addr_len)
__THROW;
is invoked regardless driver state?
y
tom
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel