From: Jeff Sutherland <jeffs@fairwayacademy.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Timeout message from kernel
Date: Fri, 13 Feb 2004 10:23:03 -0500 [thread overview]
Message-ID: <200402131023.03974.jeffs@fairwayacademy.org> (raw)
In-Reply-To: <1076682121.2671.53.camel@pegasus>
On Friday 13 February 2004 09:22, Marcel Holtmann wrote:
> > /bin> hcitool info 00:0A:4F:00:09:5E
> > Requesting information ...
> > bcsp_timed_event: Timeout, retransmitting 1 pkts
> > Can't create connection: Input/output error
> > pid 54: failed 256
> >
> > bcsp_timed_event: is a kernel error msg. I should probably try to set up
> > an l2test session properly next. Any advice?
>
> with the next update of the BCSP driver I will turn this into a debug
> message.
>
> Using l2test is easy and with -h you see all the options ;)
>
> One side: l2test -r /* listen and receive */
> Other side: l2test -s /* connect and send */
Hmmm...
[root@Arwen test]# ./l2test -w
l2test[29184]: Waiting for connection on psm 10 ...
/bin> l2test -r
l2test[79]: Waiting for connection on psm 10 ...
and there they sit, nothing happening. The SCO test works fine going either
way, however. It seems that on the ColdFire board most of the hcitool
commands fail with some kind of 'HCI...timeout' error.
Note that from ColdFire, this fails:
/bin> hcitool cc --role=s 00:0A:4F:00:09:5E
bcsp_timed_event: Timeout, retransmitting 1 pkts
Can't create connection: Input/output error
/bin> hcitool con
Connections:
But from the pc, I get this:
[root@Arwen test]# hcitool cc --role=m 00:0A:4F:00:13:5F
Can't create connection: Connection timed out
But now running 'hcitool con' on Coldfire gives this:
/bin> hcitool con
Connections:
> ACL 00:0A:4F:00:09:5E handle 40 state 1 lm SLAVE
and from the pc:
[root@Arwen test]# hcitool con
Connections:
< ACL 00:0A:4F:00:13:5F handle 41 state 1 lm MASTER
So it seems that hcitool <> hcid, or userland <> kernel is messed up on
ColdFire, is that correct? Remember I'm still a newbie at this...
Regards,
-Jeff
--
Secure your email with Gnu Privacy Guard and Mozilla, the open source
cross platform solution for Windows, Linux, and Mac OS X.
See http://enigmail.mozdev.org/
next prev parent reply other threads:[~2004-02-13 15:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 21:36 [Bluez-users] Timeout message from kernel Jeff Sutherland
2004-02-13 0:14 ` Marcel Holtmann
2004-02-13 14:17 ` Jeff Sutherland
2004-02-13 14:22 ` Marcel Holtmann
2004-02-13 15:23 ` Jeff Sutherland [this message]
2004-02-13 15:28 ` Marcel Holtmann
2004-02-13 23:19 ` Jeff Sutherland
2004-02-13 23:40 ` Marcel Holtmann
2004-02-13 23:58 ` Jeff Sutherland
2004-02-14 0:06 ` Marcel Holtmann
2004-02-14 4:10 ` Jeff Sutherland
2004-02-14 8:53 ` Marcel Holtmann
2004-02-14 13:59 ` Jeff Sutherland
2004-02-14 15:02 ` Marcel Holtmann
2004-02-15 22:43 ` Jeff Sutherland
2004-02-15 23:36 ` Marcel Holtmann
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=200402131023.03974.jeffs@fairwayacademy.org \
--to=jeffs@fairwayacademy.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.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